<p>Michael kicks things off from a proper setup. Damashe kicks things off from a boom arm clamped to his nightstand — because he's mid-move and the show must go on.</p> <p>From there, the conversation covers a lot of ground: Michael is beta testing Quill, a new cross-platform Markdown writing app from BITS that runs on Mac and Windows, written entirely in Python. Damashe shares a LaunchBar trick he'd never tried before — copying and moving files entirely within LaunchBar — and it turns out it works exactly the way it should.</p> <p>Then things get into the meat of the episode. Michael has been building a podcast app using Claude as his primary coding tool. He's not an iOS programmer, but he can develop an iOS app — and that distinction matters. Accessibility has been part of the project from day one, including a rule in his <a href="http://CLAUDE.md" rel="nofollow">CLAUDE.md</a> file that every code change gets run through the accessibility agents from <a href="http://community-access.org" rel="nofollow">community-access.org</a> before anything moves forward. No unlabeled buttons. No accessibility regressions. Just a rule that runs automatically.</p> <p>That leads to a bigger question: with AI tools making it easier than ever to build software, what excuse do developers actually have for shipping inaccessible apps? Michael makes the case that it's not a knowledge problem anymore. It's a willingness problem.</p> <p>Damashe pushes back on the "just vibe code it" framing. He has no problem with using AI to build things — he's doing it himself. What he takes issue with is the negligence: shipping code you haven't tested, don't understand, and haven't checked for security or accessibility, then asking someone else to deal with the fallout. Open source maintainers are already feeling this. Bug bounty programs are drowning in low-quality AI-generated reports. The tool isn't the problem. The behavior is.</p> <p>They also get into feedback — what it's like to receive bug reports when you're the one who built the thing — and Damashe shares the story of how he got Marco Arment to add rotor actions to Overcast, one conversation at a time.</p> <p><strong>Links and things mentioned:</strong></p> <ul> <li><a href="https://bits-acb.org/" rel="nofollow">Quill (BITS Markdown writing app for Mac and Windows)</a></li> <li>LaunchBar — <a href="https://www.obdev.at/products/launchbar/" rel="nofollow">https://www.obdev.at/products/launchbar/</a></li> <li><a href="https://community-access.org/docs.html" rel="nofollow">community-access.org accessibility agents</a></li> <li>Overcast — <a href="https://overcast.fm" rel="nofollow">https://overcast.fm</a></li> <li><a href="https://technicallyworking.show" rel="nofollow">Technically Working —</a></li> </ul> <h1>Episode Notes</h1> <p>Notes go here</p> <p>Support Technically Working by contributing to their tip jar: <a href="https://tips.pinecast.com/jar/technically-working" rel="payment nofollow">https://tips.pinecast.com/jar/technically-working</a></p> <p>Find out more at <a href="https://technically-working.pinecast.co" rel="nofollow">https://technically-working.pinecast.co</a></p> <p>Send us your feedback online: <a href="https://pinecast.com/feedback/technically-working/6a089d48-76a4-43f5-b8af-6e63343769a8" rel="nofollow">https://pinecast.com/feedback/technically-working/6a089d48-76a4-43f5-b8af-6e63343769a8</a></p> <p>This podcast is powered by <a href="https://pinecast.com" rel="nofollow">Pinecast</a>. Try Pinecast for free, forever, no credit card required. If you decide to upgrade, use coupon code <strong>r-431b7d</strong> for 40% off for 4 months, and support Technically Working.</p>