<?xml version="1.0" encoding="UTF-8"?><rss xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:atom="http://www.w3.org/2005/Atom" version="2.0" xmlns:cc="http://cyber.law.harvard.edu/rss/creativeCommonsRssModule.html">
    <channel>
        <title><![CDATA[Stories by Birdo on Medium]]></title>
        <description><![CDATA[Stories by Birdo on Medium]]></description>
        <link>https://medium.com/@itsbirdo?source=rss-a7d92b9de46d------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*_OfkpTHZ_tbzr1Zdi1n7DA.jpeg</url>
            <title>Stories by Birdo on Medium</title>
            <link>https://medium.com/@itsbirdo?source=rss-a7d92b9de46d------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Tue, 17 Nov 2026 14:13:50 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@itsbirdo/feed" rel="self" type="application/rss+xml"/>
        <webMaster><![CDATA[yourfriends@medium.com]]></webMaster>
        <atom:link href="http://medium.superfeedr.com/" rel="hub"/>
        <item>
            <title><![CDATA[I Built a Free Teleprompter for Mac]]></title>
            <link>https://medium.com/@itsbirdo/i-built-a-free-teleprompter-for-mac-70b43e1c4d8a?source=rss-a7d92b9de46d------2</link>
            <guid isPermaLink="false">https://medium.com/p/70b43e1c4d8a</guid>
            <dc:creator><![CDATA[Birdo]]></dc:creator>
            <pubDate>Fri, 13 Mar 2026 19:57:50 GMT</pubDate>
            <atom:updated>2026-03-13T19:57:50.589Z</atom:updated>
            <content:encoded><![CDATA[<p>I want to share a small side project I built today with Claude and you should download it if you present on camera. Whether that’s product demos, video calls, YouTube content, or recorded walkthroughs, if you’ve ever struggled to maintain eye contact while staying on script, this might be for you.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*FwLEcbRI-7UXTntuhklJfA.png" /><figcaption>Teleprompter</figcaption></figure><h3>What it does</h3><p>Teleprompter is a native Mac app that puts a floating window right next to your camera, near the notch on a MacBook or top-center on any display. You paste your script in, hit start, and talk. The app listens to your microphone and scrolls the text forward while you’re speaking. Stop talking and it stops scrolling. That’s the whole interaction.</p><p>The important detail is that the window is invisible during screen sharing. Zoom, Google Meet, Teams, none of them can see it. Your audience gets your slides or your application. You get your script. Nobody knows.</p><p>There’s no account to create, nothing gets uploaded anywhere, and the app never makes a network request. Everything happens locally on your machine.</p><h3>Building it</h3><p>The whole thing came together in a single sitting. I used Swift and SwiftUI, keeping it as lean as possible with no external dependencies. The floating window sits above everything else without stealing keyboard focus, and one line of code makes it invisible to screen capture.</p><p>The voice detection was the most interesting part to get right. Rather than full speech recognition, the app monitors your microphone volume level. When it crosses a threshold, it scrolls. When it drops, it stops. Simple in concept, but getting it to feel right took a fair amount of iteration. Raw audio levels are noisy, they spike and drop between syllables, which makes the scrolling stutter if you’re not careful. Some signal smoothing and a short hold timer to bridge natural pauses between words sorted that out. The scroll also eases in and out rather than snapping on and off, which makes the experience feel natural rather than mechanical.</p><p>Just as it’s essential to iterate on your product, I found the same applied here. The sensitivity slider ended up being the most important control in the whole app. Everyone’s microphone, voice, and environment are different. What works in a quiet home office doesn’t work in a coffee shop. Having that adjustment front and centre, not buried in a settings menu, made a big difference in usability.</p><h3>What I learned</h3><p>The thing that surprised me the most was how much of the work was tuning, not building. The core functionality came together quickly. But making it feel good? That was a series of small adjustments over and over again. How fast should the scroll stop when you pause? How sensitive should the default mic threshold be? How long should the app keep scrolling between words so it doesn’t stutter during natural pauses?</p><p>This took a lot of iteration to get right, but I think we’re at a very desirable state, also allowing for custom controls and modififcation.</p><h4>It’s free and open source</h4><p>I’ve open sourced the whole project on GitHub. Download it, build it from source, or fork it and make it your own. It runs entirely offline with zero data collection.</p><p>**GitHub:** <a href="https://github.com/itsbirdo/teleprompter">https://github.com/itsbirdo/teleprompter</a><br>**Download:** <a href="https://github.com/itsbirdo/teleprompter/releases/tag/v1.0.0">https://github.com/itsbirdo/teleprompter/releases/tag/v1.0.0</a></p><p>If you do any kind of presenting on camera, whether it’s work calls, content creation, or recorded demos, give it a try. It’s the kind of tool that disappears once it’s working, which is exactly the point.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=70b43e1c4d8a" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[My Claude Code Workflow: Why I Never Let It Write Code First]]></title>
            <link>https://medium.com/@itsbirdo/my-claude-code-workflow-why-i-never-let-it-write-code-first-4fc29f37296d?source=rss-a7d92b9de46d------2</link>
            <guid isPermaLink="false">https://medium.com/p/4fc29f37296d</guid>
            <dc:creator><![CDATA[Birdo]]></dc:creator>
            <pubDate>Wed, 25 Feb 2026 07:36:03 GMT</pubDate>
            <atom:updated>2026-02-25T07:36:03.984Z</atom:updated>
            <content:encoded><![CDATA[<p>I want to share my current Claude Code workflow for most projects, based on what I’ve found works well after prompting most days in 2026. <br>It’s a six-step process that might seem like overkill at first glance, but it consistently produces better results than the alternative, which for most people is opening Claude Code and immediately asking it to start building something.</p><p>The core idea behind this workflow is simple: <strong>don’t let Claude write a single line of code until the plan is solid</strong>. Separate research, planning, and implementation into distinct phases, each in their own clean context. It’s slower upfront, but the output quality is meaningfully better.</p><p>Just as it’s essential to iterate on your product, I believe it’s also important to iterate on how you work with AI tools. The way you prompted ChatGPT to search the web for you 6 months ago isn’t how you prompt it today. The same applies to Claude Code, your workflow should evolve as you learn what gets the best output.</p><h3>The problem with jumping straight to code</h3><p>The main issue in my experience is that most people treat Claude Code like an autocomplete on steroids, throw in a few lines, let it rip, and hope for the best. Sometimes this works for small tasks, but for anything of substance you end up in a back-and-forth of corrections, regressions, and context windows that bloat beyond usefulness. The model loses track of what it’s doing, you lose track of what you’ve asked for, and the end result is a codebase that needs significant rework. Something my friends and I have also noticed is the closer Claude gets to the end of the context window, the worse the results.</p><p>This is less about Claude’s capabilities and more about how context windows actually work. When you mix research, planning, and coding into one conversation, the model is juggling too many concerns at once. It’s the AI equivalent of context switching, and just like with human teams, it degrades the quality of everything.</p><h3>The six-step workflow</h3><p>Here’s how I currently structure most projects in Claude Code:</p><h4>1. Research the subject material</h4><p>I start a new Claude Code project with one purpose, research. The goal is to produce an output document in markdown. This could be a design system, a feature list, a competitive analysis, whatever the project needs. The important thing is that the output is a structured document I can reference later.</p><p>The key here is telling Claude to ask me questions. I don’t just dump a brief and walk away. I let it interrogate the problem space, surface assumptions I didn’t know I had, and build a shared understanding of what we’re actually trying to achieve. The back-and-forth at this stage sharpens the research output considerably.</p><h4>2. Plan from the research, no code</h4><p>New Claude instance, clean context. I write out the basic format of my idea, in as much detail as possible, telling claude not to write any code, but to ask me further questions to better pull the ideas and edge cases ouf of my head.</p><h4>3. Plan + Research</h4><p>New Claude instance, clean context (notice a pattern here?)<br>Next I feed in the research doc from step one and tell Claude to update the plan and to identify any gaps, missed features or rabbit holes. Again explicitly, no code yet. I get claude to update the plan.MD file.</p><p>Again, I tell it to ask questions. This is where a lot of the value comes from. Claude will catch gaps between the research and what actually needs to be built. It’ll ask about edge cases, priorities, and constraints that didn’t come up during the research phase. These questions often reshape the plan in ways I wouldn’t have anticipated, which is exactly the point.</p><h4>4. Manual review</h4><p>This is the human checkpoint. I read the plan myself and confirm that things make sense — that Claude is on the right track and hasn’t over-engineered something, or missed the point entirely.</p><p>This step isn’t glamorous, but it might be the most important one. No amount of clever prompting replaces actually reading the plan with your own eyes and validating that the approach feels right. If something seems off, I’ll adjust it or flag it before moving forward.</p><h4>4. Fresh context review</h4><p>Again, new instance, new context. Ask Claude to review the plan markdown and improve it. More questions.</p><p>This is a subtle but powerful move. Every time you re-enter with a clean context, Claude reads the plan without the baggage of the conversation that produced it. It’s reading the document cold, the same way another engineer would if you handed them a spec. It catches things it wouldn’t have caught mid-flow.</p><h4>5. Model switch for a second opinion</h4><p>Exit context again, switch from Opus to Sonnet, and ask for another review of the plan. Different model, different perspective. Sonnet tends to be more concise and practical in its feedback, it’ll flag things that Opus might have over-engineered or glossed over.</p><p>I find this step particularly valuable because it’s essentially getting a second opinion from a different “mind”. The models have different strengths and tendencies, and running the plan through both surfaces issues that either one alone might miss.</p><p>More questions. Always more questions.</p><h4>6. Now Claude can write code</h4><p>Back to Opus. At this point the plan has been researched, written, manually reviewed by me, reviewed by Claude twice across separate contexts, and stress-tested by a different model. Now, and only now do I ask Claude to start working on the plan (obviously with a clean context!)</p><p>By this stage, the plan is tight enough that Claude can execute with minimal course correction. The code output is cleaner because the thinking was cleaner. There’s less back-and-forth, fewer dead ends, and the context window stays focused purely on implementation rather than being polluted with planning conversations from earlier in the process.</p><p>If you’re feeling brave, run this claude instance by typing `claude — dangerously-skip-permissions` claude won’t prompt you for anything and just get on building.</p><h3>Why separate contexts matter</h3><p>The context window is your most valuable resource when working with Claude Code, and you burn through it fast when you’re mixing concerns in the same session. Research conversations generate a lot of exploratory text. Planning conversations generate a lot of structural back-and-forth. Neither of these are useful context when you’re actually writing code, they’re noise.</p><p>By separating each phase into its own instance with a clean context, Claude is always operating with maximum focus on the task at hand. The markdown documents become the handoff mechanism between phases, which also means you have a paper trail of the thinking that went into the project.</p><h3>Iterate on your workflow, not just your product</h3><p>This workflow won’t be the right approach for every project. Quick scripts, small fixes, and simple features probably don’t need six steps. But for anything with real complexity, a new product, a significant feature, a system redesign, taking the time to research and plan before writing code pays for itself many times over.</p><p>Like everything in product development, ship it, learn from it, and iterate. This is my current workflow, not my forever workflow. As the tools improve and as I learn more about what works, it’ll change. The important thing is being intentional about the process rather than defaulting to the fastest path and hoping for the best.</p><p>If you’re finding that Claude Code produces inconsistent results or goes off the rails on larger projects, consider trying this approach. Separate the thinking from the building, and give both the space they deserve.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=4fc29f37296d" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Vibe coding on Polkadot]]></title>
            <link>https://medium.com/@itsbirdo/vibe-coding-on-polkadot-14392f18efe4?source=rss-a7d92b9de46d------2</link>
            <guid isPermaLink="false">https://medium.com/p/14392f18efe4</guid>
            <dc:creator><![CDATA[Birdo]]></dc:creator>
            <pubDate>Mon, 26 Jan 2026 21:51:49 GMT</pubDate>
            <atom:updated>2026-01-26T21:51:49.574Z</atom:updated>
            <content:encoded><![CDATA[<p>Today I built a dApp that takes DOT on Polkadot Hub, sends it to the Hydration blockchain via XCM, and buys gold (PAXG).</p><p>The whole thing took a few hours using Claude Code and the Opus 4.5 model, here’s how it came together.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/444/0*if1uqRJYM-mH4e6D" /><figcaption>Mobile view of the dapp</figcaption></figure><h3>The Goal</h3><p>I wanted to build something simple that solved one specific use case: buying gold. Applications have been trending towards more discrete usecases and I thought this was a perfect approach.</p><p>This could absolutely be expanded later to bridge in EVM assets or support additional swap routes, but for now the focus was on getting the core flow working. The UI is still just the raw Claude interface, but that will get styled into something much nicer down the road.</p><h3>Planning Before Coding</h3><p>I started by putting Claude in plan mode with strict instructions not to write any code yet. Before touching implementation, I wanted a solid blueprint.</p><p>I fed Claude three key repos:</p><ul><li><strong>Hydration Codex</strong> (<a href="https://github.com/galacticcouncil/hydration-codex">https://github.com/galacticcouncil/hydration-codex</a>) for the DEX swap functionality</li><li><strong>ParaSpell’s XCM Router</strong> (<a href="https://github.com/paraspell/xcm-tools/tree/main/packages/xcm-router">https://github.com/paraspell/xcm-tools/tree/main/packages/xcm-router</a>) for handling cross-chain transactions</li><li><strong>PAPI</strong> for wallet connections and transaction signing</li></ul><p>With this context loaded, Claude generated an initial plan. But I didn’t stop there.</p><h3>Iterating on the Plan</h3><p>I took that first version, restarted the Claude session entirely, and asked it to review the plan with fresh eyes. Find faults, add more detail, challenge the assumptions.</p><p>I’ve found that iterating on the plan multiple times with new context dramatically improves the output. Each pass catches blindspots you would have discovered painfully during implementation. Also another tip that seems to work well is to use one of the other models to review your plan, type /model and try checking in Sonnet.</p><p>After several iterations, the plan felt solid, it was time to pull the trigger.</p><h3>Building</h3><p>I opened a new context, input the finalized plan, and told Claude to go.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*hLPAgV-ER1UqVeaoN5NfZA.png" /></figure><p>Claude was ready with something to show me on localhost.</p><p>A white screen.</p><p>Okay then….</p><h3>Debugging and Troubleshooting</h3><p>This is where things got interesting. Here’s a tip that saved me a ton of time: I had Claude add a small debug window at the bottom of the UI that displayed errors in real-time. This let me copy and paste issues directly into Claude without constantly diving into the browser console.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/875/0*rO9wKs1gMVvEbTxm" /></figure><p>With that feedback loop in place, troubleshooting became much smoother. I worked through several issues:</p><ul><li>Fixed the UI rendering problems</li><li>Fixed Claude hammering the Coingecko API too aggressively</li><li>Fixed asset naming mismatches between ParaSpell and Hydration</li><li>Got the quoting function working properly</li></ul><p>Each fix brought me closer to something functional.</p><h3>The Moment of Truth</h3><p>PAPI integrated perfectly, hats off to the team, their documentation is really excellent. Wallet connection was seamless. The actual transaction signing implementation just worked.</p><p>I got the wallet popup, signed the transaction, and hoped for the best.</p><p>Given I was doing a relatively complex on-chain transaction spanning three different repos and two blockchains, I was skeptical to say the least.</p><p>I checked the block explorer.</p><p>It worked.</p><p>I checked my on-chain gold balance.</p><p>It was there. The swap actually worked.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/505/0*ol7F48491OKVdGPL" /></figure><h3>What This Means</h3><p>We are in the age of personalized software. A few hours of focused work with the right tools and I had a working cross-chain dApp that solves a real use case.</p><p>This will be polished, expanded, and improved. Who knows where you might see it next.</p><p>The barrier to building useful software has never been lower. The question is no longer “can I build this?” but “what should I build?”</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=14392f18efe4" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Polkadot App — July 25' Update]]></title>
            <link>https://medium.com/@itsbirdo/polkadot-app-july-25-update-46c9c1b3c038?source=rss-a7d92b9de46d------2</link>
            <guid isPermaLink="false">https://medium.com/p/46c9c1b3c038</guid>
            <dc:creator><![CDATA[Birdo]]></dc:creator>
            <pubDate>Fri, 08 Aug 2025 08:37:48 GMT</pubDate>
            <atom:updated>2025-08-08T08:37:48.947Z</atom:updated>
            <content:encoded><![CDATA[<h3>Polkadot App — July 25&#39; Update</h3><p>Hi everyone,</p><p>Here’s the July update on the Polkadot App on behalf of the Polkadot Community Foundation.</p><p><strong>Is it live? </strong>Not yet.<br><strong>Is it close?</strong> Yes.<br><strong>Are you actually going to release it?</strong> Yes of course! We want this to be live more than anyone!<br><strong>Why is it taking so long?</strong> We decided to audit an additional piece of code, which was the right thing to do, but this unfortunately takes more time. We are working with Oak Security who have an excellent standing in the security field and the good news is they are finishing the first phase of the audit this week. <br><strong>Has the app been approved by Apple and Google? </strong>Yes it’s approved and now ready to go, pending the results from the audit!</p><p><strong>What have you been doing in the meantime?</strong> As per the last update, we have been working on gifting. <br>Gifting will let users easily send DOT to friends or family. Moreover, it’s a simple, convenient way to introduce new people to Polkadot. Most of the work is already complete, and the feature is expected to roll out shortly after the app launches in the U.S.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/293/1*Y-iliojVu-dsyZnfTI7BjA.png" /></figure><p><strong>What else have you been working on?</strong></p><ul><li>After we finish gifting, we will be starting work on the UI and integration for the highly anticipated Polkadot Visa card. This will be a reasonable amount of work and will likely take two to three months to complete.</li><li>We have submitted the Polkadot Visa card design docs to Visa via our partner Baanx and are waiting on confirmation. This doc contains the card design and all specifics around look and feel of the virtual and physical card 👀</li><li>We have been cooking up a more detailed roadmap to share as many people have asked about future plans for the app. We’ll share this soon.</li><li>We’ve also been working on the next phases of country rollout — more on this soon!</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*nBDzXMW8NHZm7j2K6faDHw.png" /></figure><p>We are honestly so, SO excited to finish this first version and get it live. We have spent so much time and effort designing, building and testing the application and supporting services, sorry we’re not quite there yet but no-one wants to see this live and being used more than us.<br>Thanks for your patience and support, looking forward to sharing more next month!</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=46c9c1b3c038" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Scaling Product Teams]]></title>
            <link>https://medium.com/@itsbirdo/scaling-product-teams-b89094d64d14?source=rss-a7d92b9de46d------2</link>
            <guid isPermaLink="false">https://medium.com/p/b89094d64d14</guid>
            <dc:creator><![CDATA[Birdo]]></dc:creator>
            <pubDate>Sun, 15 Jun 2025 04:10:19 GMT</pubDate>
            <atom:updated>2025-06-15T04:10:19.807Z</atom:updated>
            <content:encoded><![CDATA[<h3>Scaling Product Teams</h3><p>I want to share my thoughts on team structure for lean start-ups building mobile (or web) consumer-facing products, based on my 12 years of experience. I propose a new two team structure that I believe could be a great benefit for small product teams of 10–30+ people.</p><p>Just as it’s essential to iterate on your product, I believe it’s also crucial to refine your team’s design and test different compositions, structures, and frameworks. An arrangement that works for 6 people likely won’t work for 50 people. As the product team grows, so do your methodologies and team structures.</p><p>This two team structure can balance strategic work and BAU (business as usual) tasks as they arise, ensuring that the product drives forward strategic product goals, but the hard work already expended on developing product features doesn’t go to waste. In this article, I’ll explain why most team structures don’t scale, how others currently operate, and why I think this two-team model can be better.</p><h3>No single team structure works forever</h3><p>The main issue in my experience is teams either focus too heavily on large strategic work or mostly only spend their time refining the existing product. It mostly seems to be an all or nothing approach between one of these extremes. For example at one company I worked for, the product direction was ONLY to break new ground and deliver new features, and on the flip side in another company I worked for, we re-built the onboarding experience at least 4 times in the first year of the product life but didn’t have anything interesting to announce for months at a time.</p><p>This post is less about agile vs waterfall vs shapeup vs any other methodology, but more about the thinking that goes into setting teams up for successful products. The structure of the team has a big role in the ownership of the product and how connected teams are to what they are building. Not every structure works in every team environment, the more external forces and contractors you have working in the team, the more the dynamic changes and their own company values, culture, and working environments come into the mix. As product teams grow, their structure, processes, and team makeup also need to change and iterate.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/498/0*L8fa8K8qEB1LmVKp" /></figure><h3>What structures exist now?</h3><p>These are some of the main team structures and how they iterate as the company grows:</p><ol><li>The “do all” team. For small start-ups, there is one product team and they work on everything from building new features, maintaining old features, providing user support, you name it, they do it. This is likely the typical team structure for practically every start-up.</li><li>Feature teams. The typical migration from the “do all” team is to organise teams into feature teams. As the company grows and finds success, it adds more product managers and puts them in charge of individual teams focused on one feature in the product. This could be just two product teams working through different features as the product grows, or it could be 20 product teams working on existing features to tune and refine them. This also seems to be the way that some mega orgs, such as Uber structure their teams. For example, my friend worked at Uber, specifically on the “Driver referrals” feature of the application, that’s the only feature he worked on, for four years.</li><li>Vertical squads. Another interesting example of team structure is where a team owns a vertical stack across multiple products and channels. This only really works for larger orgs that have many teams and products and an org that can afford bigger teams. For example, when ANZ X was being built they had a team that managed “Customer Onboarding” across all products (web, mobile, in-store, physical mail, communications, etc), this allowed the team to ensure the experience across any product was consistent and suitable to the form factor or environment the customer was in. These vertical teams typically tend to be fully cross functional, for example in the banking example, the product team would also feature legal, risk management, and other “non” typical software roles, they tend to be many teams making up a “vertical”.</li></ol><p>As the “do all” team grows bigger, they typically transform into “feature teams”. They have to constantly make decisions between building new functionality or improving on old functionality and this can cause issues where features become unmaintained, potentially stop working, or don’t get the continued love they deserve (why spend the money and energy building it in the first place if it’s not to be maintained long term?). There is ongoing context switching between these two modes.</p><p>So how can we grow the product team without going straight from a “do all” team to a “feature team”?</p><h3>Two teams, one product: Strategic &amp; BAU</h3><p>The “two team” structure is a more modern / agile approach to the “handover to BAU” in traditional waterfall projects, where once a product is delivered, it’s handed over to another team to run and manage. As the product team grows, this can be implemented to allow for better focus between the teams. This structure is an excellent in-between transition from the “Do all” to “Feature teams”</p><p>You can achieve this structure with just two product teams (two PMs and a small group of devs in each team (2–4)) and can allow for the company / product to advance with strategic work, but ensure that the existing product receives improvements and optimisations.</p><p>In this proposed structure there are two (or more) product teams, one product team is focused on strategic work, they are building the impactful, marketing driving work that the company can announce and drive eyeballs towards the product. They might not ship anything to production for a month or more. The other team is focused on ensuring the product is performing well, conversions are happening, features are being used and the existing experience is excellent. This data driven team has the agency to touch any part of the product, run A/B tests, and ultimately could be considered the product SRE team.</p><p>This structure I feel also scales well as the product grows, this could allow for a small product team to focus on <em>really</em> strategic product features (similar to Google moonshot program) while other product teams build out parts of the roadmap or product vision, and other product teams manage different features or functions.</p><p><strong>Pros:</strong></p><ul><li>Each team is given a deep focus to execute on across product design, thinking, and development.</li><li>This structure works well while the team is growing.</li><li>It ensures the product is well maintained and previous development efforts continue to improve in their value.</li><li>This structure works well for all modern product development</li></ul><p><strong>Cons:</strong></p><ul><li>Some individuals don’t want to work on BAU tasks all the time, so switching team members occasionally might be required.</li><li>This process requires more and deeper documentation of the product (maybe not a bad thing!) but could lead to a small reduction in delivery speed.</li></ul><p>As the product team grows further, decisions can be made about where to deploy the new teams. E.g. in an established small product with great product market fit, spending additional resources to improve the onboarding and first time purchase conversion might yield better benefits over building a new feature.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/705/1*0m3Cj0ilhlLZljXtfJRafw.png" /></figure><h3>Evolve Your Team Like Your Product</h3><p>Just as no product reaches success by standing still, no team structure should remain static as a company grows. The transition from “do all” teams to another structure is inevitable as the company grows, but how you manage that transition matters.</p><p>The two-team model where one team is focused on strategic growth, while the other on continuous improvement gives your product the ability to advance meaningfully while maintaining the quality and performance that users expect.</p><p>This approach won’t solve every organizational challenge, but it offers a sustainable and scalable way to navigate the growing pains of early-stage product development. It protects your long-term product investment while still giving space for innovation and strategic wins.</p><p>If you’re building a lean team in a fast-moving environment, consider testing this model. Like everything in product development — ship it, learn from it, and iterate.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=b89094d64d14" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Polkadot App — May Update]]></title>
            <link>https://medium.com/@itsbirdo/polkadot-app-may-update-f35824e12792?source=rss-a7d92b9de46d------2</link>
            <guid isPermaLink="false">https://medium.com/p/f35824e12792</guid>
            <dc:creator><![CDATA[Birdo]]></dc:creator>
            <pubDate>Mon, 02 Jun 2025 18:59:31 GMT</pubDate>
            <atom:updated>2025-08-08T08:30:20.388Z</atom:updated>
            <content:encoded><![CDATA[<h3>Polkadot App — May 25&#39; Update</h3><p>Hello all, here’s the May update on the Polkadot App from the Polkadot Community Foundation! These updates are to make sure everyone is up to date and has deeper insight into what we’re working on.</p><p>So, big news, we have submitted the apps to Apple and Google — the launch is imminent <em>and will take place next month</em>!!!!!!! (Aug 25&#39;: or so we thought….)</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/510/1*Von_oTJoH84q3c71Rd7bJA.png" /><figcaption>USA Launch Imminent</figcaption></figure><p><strong>About the app</strong></p><p>If you haven’t heard of the Polkadot App before, it’s a mobile app built for newcomers and existing crypto users to provide an easy entry into Polkadot and crypto more broadly. <br>You can see more details and all the features at <a href="https://polkadot.com/app">https://polkadot.com/app</a></p><p><strong>Last months work</strong></p><p>In the last month we have been finishing everything up and getting ready for launch. As I mentioned we’ve now submitted the apps to the app store and are in the final testing stage before we launch it in the USA.</p><p>There is a<a href="https://x.com/TheKusamarian/status/1926126133558321350"> quick video run</a> through on the AAG from last week about the app and I will be publishing a deep dive into the app, covering off the features and showing how everything works next week.</p><p>Autonomous Projects who is the group managing the Polkadot Community Foundation have posted a treasury proposal through governance (<a href="https://polkadot.polkassembly.io/referenda/1573">#1573</a>) to obtain additional funding and runway to keep building into the future once we have submitted the app. There will be a representative on AAG each week while the proposal is live 🙂</p><p>The Polkadot App will feature a live chat service which is available for anyone that’s stuck or needs help — we have onboarded two community members to provide customer support!</p><p><strong>What’s next</strong></p><p>Next we are going to have a mini google meets party to celebrate the launch, it’s been a massive amount of work to get to this point! 🎉<br>We have another exciting update to share early in June too, we’re just getting our ducks in a row. We’ll pick up building the gifting flow that I demo’d last month and work on any feedback from the launch.</p><p>Thanks for listening and I hope you found this helpful!</p><p>If you want to collect this story, I’ve minted a PROOF OF SAUSAGE NFT <br><a href="https://dotmemo.xyz/claim/mayupdate">https://dotmemo.xyz/claim/mayupdate</a> which you can mint ❤</p><p>Until next month!</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=f35824e12792" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Polkadot App — April 25' Update]]></title>
            <link>https://medium.com/@itsbirdo/polkadot-app-april-25-update-8a1040ee382f?source=rss-a7d92b9de46d------2</link>
            <guid isPermaLink="false">https://medium.com/p/8a1040ee382f</guid>
            <dc:creator><![CDATA[Birdo]]></dc:creator>
            <pubDate>Wed, 30 Apr 2025 19:08:35 GMT</pubDate>
            <atom:updated>2025-04-30T19:08:35.061Z</atom:updated>
            <content:encoded><![CDATA[<h3>Polkadot App — April 25&#39; Update</h3><p>Hey everyone, here’s the monthly update on the Polkadot App from the Polkadot Community Foundation.</p><p>Surely we can’t have too many more of these before we go live right ?!</p><p>As mentioned in the last post, these updates are to help keep the community in the loop and provide more insight into our work and what we’ve been working on.</p><p>I’ll continue these even after we’re live, as once we launch there is still a lot more to build and look forward to!</p><h3><strong>About the app</strong></h3><p>As you may know the Polkadot App is a new mobile app approved by the community previously to give newcomers and existing crypto users an easy entry into Polkadot and crypto more broadly. <br>Its mission is to make Crypto simplified for you.<br>Our goal is to simplify as much of the blockchain and technical complexity as possible and really make Polkadot simple and easy to use.</p><h3><strong>Last months work</strong></h3><p>In April we had the easter break and a bit of leave from the team. <br>We have finished up staking in the app which is awesome and works super smoothly, which I’ll show off to you now.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*C_qYuP-wyDYgYWDOEZ-RbA.png" /><figcaption>The Earn flow</figcaption></figure><p>If you have staked with Polkadot before this experience should be pretty familiar. To make it normie friendly we’ve branded it as “Earn” rather than “Stake”. When the user enters the “earn” section of the app they will see the an onboarding screen, telling them how it works.</p><p>The app defaults to the max available amount to depost, or I can just type in the amount I want or switch between tokens and fiat. Then swipe to confirm, done!</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/390/1*r2ey_23Ni1fbVo9UkxyS0Q.png" /><figcaption>Deposited DOT</figcaption></figure><p>The user can then see their history, their earn rewards and withdraw their funds whenever they want subject to the usual Polkadot staking-related configurations.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/390/1*ZtvZsra8IlZAhFYq23nIxA.png" /><figcaption>The main Earn screen</figcaption></figure><p>The other main change we have been working on is feedback from the latest user testing we performed during the Polkadot Miami week. We found the in-store payments too slow and we weren’t happy to launch with the user experience. <br>However great news, we’re close to finishing a change which will decrease the waiting time for the user by around 90%.</p><p>We have hit some roadblocks with the Apple Developer account and we’re working through this with them.</p><h3><strong>What’s next</strong></h3><p>We are making one last change (fingers crossed) to how the app integrates with Asset hub, or the Polkadot Hub.</p><p>We noticed in our most recent user testing that the ED on Polkadot was an issue for users, so we’re going to default the app to using Assethub as the primary network.</p><p>This reduces the ED from 1 DOT to 0.01 DOT which is a really nice quality of life change for users. It decreases fees when transferring funds and provides overall a better experience for users.</p><p>This sets the app up to be future proof with the upcoming Assethub migration and rollout planned in Q3. We will still support the relay chain and have some tricks up our sleeve to make it seamless to the user (what else would you expect!)</p><p>Unfortunately we still don’t have a date for launch but I would estimate we’re still at least a month away with the support for Assethub.</p><p><strong>Future plans</strong></p><p>The gifting experience that I mentioned last time is ready! Here’s a screenshot from our Figma showing off how it works.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*8X_z3qf8dTHOS6O1Kte67A.png" /></figure><p>We’re working in the background on two pretty cool ?things? for the Polkadot ecosystem. Should be more info to share next month 😯</p><p>Thanks for listening and I hope you found this helpful!</p><p>Until next month 🫡</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=8a1040ee382f" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Polkadot App — March 25' Update]]></title>
            <link>https://medium.com/@itsbirdo/polkadot-app-march-25-update-c94fb8c63865?source=rss-a7d92b9de46d------2</link>
            <guid isPermaLink="false">https://medium.com/p/c94fb8c63865</guid>
            <dc:creator><![CDATA[Birdo]]></dc:creator>
            <pubDate>Thu, 10 Apr 2025 07:30:47 GMT</pubDate>
            <atom:updated>2025-04-10T09:36:59.894Z</atom:updated>
            <content:encoded><![CDATA[<h3>Polkadot App — March 25&#39; Update</h3><p>Gm gm, here’s a quick update on the Polkadot App for March 25&#39; from the Polkadot Community Foundation (PCF). To keep the community in the loop and provide more insight into our work, I’ll be sharing a monthly update outlining our recent progress.</p><p><strong>About the app<br></strong>As you may know the Polkadot App is a new mobile app we’ve been developing to give newcomers and existing crypto users an easy entry into Polkadot and crypto more broadly.</p><p>Our goal is to simplify as much of the blockchain and technical complexity as possible and really make Polkadot simple and easy to use. That’s why our new messaging is — Crypto simplified for you.</p><p>We’ll be launching initially in the US and are working hard to bring it to more of you around the world.</p><p>More info @ <a href="https://polkadot.com/app">https://polkadot.com/app</a></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*JQbFjxQLIXioKijX" /><figcaption>The Polkadot App 🤌</figcaption></figure><p><strong>Previous development<br></strong>While we had hoped to launch earlier, we encountered some unexpected complexities with setting up the Apple and Google developer accounts. This involved Apple leaving us on read for weeks and generally was a major pain in the ass. These issues have now been resolved, and the good news is that as of last week we have developer accounts set up to publish both of the apps! As a Web3 community we need to think how we can publish apps that don’t rely on centralised players like this anymore.</p><p>We have finished development of all the main features of the app and have also worked with SR labs to perform an audit of the app which returned no major findings. 🔐</p><p><strong>User testing and feedback<br></strong>Since December we have performed several rounds of user testing of the app and have been working on the feedback.</p><p>We have added DOT staking into the app prior to shipping it to improve the value proposition for people downloading and using the app. We believe the 13% rewards will help attract people to download and use the app. This added scope has obviously meant it’s taken longer to develop and ship, but we believe it will be worthwhile.</p><p>Currently we’re finishing up the staking development and making some small improvements based on feedback from the user testing.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/444/1*UgzHO8Fn30-9KUrTXcqFYA.png" /><figcaption>Easily deposit DOT (Stake) through the Polkadot App</figcaption></figure><p><strong>Launch preparations<br></strong>While we don’t have a launch date to share just yet, our priority is to ensure the Polkadot App delivers an excellent experience from day one. We’re in the final stages of preparation and will communicate the launch date as soon as we have full confidence in its readiness. We appreciate your patience and are excited to bring this to you soon. Believe me, I want this live more than anyone. 😵</p><p><strong>What’s next<br></strong>We’re currently designing the ability to easily gift DOT to friends or family and we think that it’ll be an excellent way to help onboard people to Polkadot. We’re also exploring more options for payments and have lots of things in the pipeline 👀</p><p>Thanks for listening and I hope you found this helpful! Until next month 🫡<br>Would you like to see a breakdown of the app and all the features?</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=c94fb8c63865" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Testing the Metamask Metal Credit Card in Berlin: A Hands-On Review]]></title>
            <link>https://medium.com/@itsbirdo/testing-the-metamask-metal-credit-card-in-berlin-a-hands-on-review-269724b75290?source=rss-a7d92b9de46d------2</link>
            <guid isPermaLink="false">https://medium.com/p/269724b75290</guid>
            <dc:creator><![CDATA[Birdo]]></dc:creator>
            <pubDate>Mon, 31 Mar 2025 12:58:19 GMT</pubDate>
            <atom:updated>2025-04-01T07:49:52.782Z</atom:updated>
            <content:encoded><![CDATA[<p>I’m in Berlin testing out the new Metamask Metal credit card. Cash is king here, with many restaurants still cash-only, and Germany is not known for being technologically forward (fax machines are still used here!).</p><p>Paying with crypto really feels like I’m a time traveler.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/996/1*XVHeiHgBvmR0jiWnbiCqxQ.png" /><figcaption>The beautiful metal Metamask card</figcaption></figure><p>I was super lucky to be gifted one of the first metal cards in production to try out, and I’m really interested in whether we can bring this experience to Polkadot. I’m interested to see how far we’ve come with crypto payment cards and what the gap is to making them ready for mass adoption.</p><h4>My first purchase</h4><p>My first experience was in the local supermarket, buying a white Monster and flowers for my wife 🫡</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/736/1*7eMkfW-Gc2YhgbIgW0tKJA.png" /><figcaption>Crypto to Monster</figcaption></figure><p>I have to say, making the first payment left me with a little trepidation, but it was flawless and processed in the same time I would expect any card payment to work.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/698/1*__5EOOgmu_VwFQTKBYdPww.png" /><figcaption>I am not in charge of cleaning the machines</figcaption></figure><p>Everyone I’ve shown the card to has been suitably impressed by the quality. The design is simply stunning, and the Apple Pay version is cool and quite fun.</p><h4>About the card</h4><p>The Metamask credit card is a non-custodial payment card that lets you pay in USDC anywhere MasterCard is accepted. It uses smart contracts to authorize the spend in your wallet without forcing you to deposit funds into a smart contract. It features cashback for the metal card of up to 3% USDC, however the card only uses Linea network, which is another Consensys product (like Metamask).</p><h4>The pros</h4><ul><li><strong>Beautiful design</strong>: The card is beautiful, with attention to detail that makes it feel premium with a satisfying weight to it.</li><li><strong>Seamless payments</strong>: Paying was easy, simply tapping the card felt like any other payment experience. It worked just as you would expect a normal credit card to.</li><li><strong>Impressive UI</strong>: The web UI for managing the card is really nice. It’s informative, detailed, and clean, not what you would typically expect from a Metamask product.</li><li><strong>Reasonable gas fees</strong>: Gas on Linea was cheap, about the same as a Polkadot roll-up, though having to keep an ETH gas balance on a new network just for payments is a major inconvenience.</li></ul><h4>The Cons</h4><ul><li><strong>Linea</strong>: Using Linea was a pain. Coming from Polkadot where I can typically pay gas in any token, having to bridge ETH to the wallet just to pay gas was a headache.</li><li><strong>Slow bridging</strong>: Bridging was a slow process — this is typical for Ethereum, but waiting 20 minutes for funds to appear in my wallet is never a great feeling. The bridging options / products (I found) were also quite limited. Having money in limbo is never a great feeling as a user.</li><li><strong>Web management UI</strong>: Nothing is built directly into the Metamask app for card management or setup. Maybe this is due to me getting an early version, but having to manage everything via a web UI, INSIDE THE APP which requires me to log in again is clunky.</li><li><strong>Public transactions</strong>: Payments are still public. We will not see mass adoption with public payments, end of story.</li></ul><h4>Metamask vs competitors?</h4><p>As mentioned before, the majority of payment cards are custodial, this already puts the Metamask card at a large advantage vs the rest of the consumer crypto card space. Do the majority of people care about this? Probably not until a hack or exploit and they have their funds stolen or compromised, but they should.</p><p>The metal card I’m testing with also has close to no fees, no monthly account fee, no transaction fee and paying in EUR with USDC feels like it has little to no FX rate. Cashback is also in USDC, up to 3% on spending with the premium metal card.</p><p>Overall the Metamask card feels more normie friendly than say the Gnosis pay card.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/736/1*iFXP8xye8WSxW9AkCUpTHA.png" /></figure><h4>What can we improve on Polkadot?</h4><ol><li>In reviewing the major payment cards available, I’ve noticed almost all of them are custodial cards. While this works, I’d argue all payment cards in the future should be non-custodial to protect users.</li></ol><p>2. Gas fees and transaction fees should be payable in USDC — requiring a separate token for gas creates a poor user experience. — Getting funds to the chain the card is hosted on should be easy, with a simple DEX available for swapping in and out of USDC.</p><p>3. We need private payments. Simple as that.</p><h4>Looking forward</h4><p>This card represents a first step in a major rebranding that Metamask is undertaking to update their brand look, feel, and promise to users. Unfortunately, the product remains largely the same under the shiny new coat of paint. While the card itself is slick and well-executed, the main issues still stem from the Metamask wallet and the underlying Ethereum infrastructure for payments.</p><p>As crypto payment solutions continue to evolve, addressing these pain points will be crucial for achieving the web2 experience necessary for “mainstream adoption”. The Metamask card shows promise, but there’s still room for improvement, especially if we can crack private payments on Polkadot.</p><p>What would you like to see in a crypto payment card?</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=269724b75290" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[How to get Polkadot Testnet tokens (on Paseo)]]></title>
            <link>https://medium.com/@itsbirdo/how-to-get-polkadot-testnet-tokens-on-paseo-8c2fbe45b603?source=rss-a7d92b9de46d------2</link>
            <guid isPermaLink="false">https://medium.com/p/8c2fbe45b603</guid>
            <category><![CDATA[cryptocurrency]]></category>
            <category><![CDATA[web3]]></category>
            <category><![CDATA[polkadot]]></category>
            <category><![CDATA[developer-tools]]></category>
            <category><![CDATA[testnet]]></category>
            <dc:creator><![CDATA[Birdo]]></dc:creator>
            <pubDate>Mon, 12 Feb 2024 15:56:26 GMT</pubDate>
            <atom:updated>2024-02-12T15:58:32.635Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*5PEA7WjJtHEgEGiQ-fL9Hg.png" /><figcaption>Replacing Rococo, Paseo is the new developer testnet run by the community</figcaption></figure><p>Paseo, the newest Polkadot testnet, has successfully launched and I’ll show you how to claim testnet tokens to get building on the network. Paseo is open to all, anyone can launch an appchain (parachain) on the network as part of their deployment process to launch on Polkadot.</p><p>Paseo is the newest Polkadot development testnet, replacing Rococo and ultimately contributing to the development of a more reliable and robust environment for deployment on Polkadot.</p><p>Paseo has launched in 2024 and is currently undergoing a <a href="https://polkadot.polkassembly.io/referenda/464">governance vote</a> to provide funding to the distributed community teams that will be maintaining the network. This guide will show you how to get setup and building on the testnet.</p><ol><li>You’ll need a Polkadot Wallet — I always recommend the <a href="https://talisman.xyz/">Talisman wallet</a> it’s super easy to get setup. Head to Talisman.xyz and download the wallet.</li><li>Once downloaded and setup, open the settings, navigate to “Networks” and enable Testnets.</li></ol><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*qnPUv3gmb2H1IEaWTpB_Tw.jpeg" /><figcaption>1. Click, Networks and Tokens. 2. Enable Testnets</figcaption></figure><p>3. In Talisman, open the wallet and click the two squares to copy your wallet address.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*ln-SfW5-3kgjaXXhdV0WWw.png" /><figcaption>Click the squares next to your account to open the copy address screen</figcaption></figure><p>4. Search Paseo in the box that appears, then click “Copy Address” at the bottom of the screen.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/974/1*uII7900DlkmIT-NnmTm37A.png" /></figure><p>4. <a href="https://paritytech.github.io/polkadot-testnet-faucet/paseo">Head to the Polkadot Faucet</a>, select “Paseo” as the network and then enter your address.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*3SfG5_nI_LCXqHeDNddk7A.jpeg" /><figcaption>Select the network and then paste in your address</figcaption></figure><p>5. All done! You will now have the PAS in your wallet, open Talisman to view it.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*MJczNC20IAxfFbusjIaSIA.png" /></figure><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=8c2fbe45b603" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>