Skip to content

Episodes

#167: We're Going to Atlanta

<p>This week, Mike and Damashe dig into Earshot build 99, react to WWDC 26, and ask the big question: are AI agent devices actually ready to replace your phone? Spoiler: your ride might end up in the wrong city.</p> <p><strong>What We Talked About</strong></p> <p><strong>Earshot Update - Build 99</strong></p> <ul> <li>The new alphabetical library picker is live, with a count of how many podcasts are under each letter</li> <li>Per-podcast playback speed is now working: set a default speed, override it for individual shows, and it remembers your preference automatically</li> <li>The database migration bug from builds 88-95 is fixed; if your app was spinning and crashing, update to build 99</li> <li>The app now gives you a useful error message instead of just failing silently if something goes wrong with the database</li> <li>If you are on TestFlight and want to send feedback, email feedback@technicallyworking.show - do not use the TestFlight feedback form, because Mike cannot reply to you there</li> <li>To get on the beta, find Michael on Mastodon</li> </ul> <p><strong>Apple Deals Worth Knowing</strong></p> <ul> <li>AirPods Pro 3 spotted at $179 on Amazon, Best Buy, and possibly Walmart</li> <li>AirPods 4 at $99</li> <li>Apple Watch Series 11 (42mm GPS) at $299</li> </ul> <p><strong>WWDC 26 Impressions</strong></p> <ul> <li>Mike went in with low expectations and came out a little underwhelmed</li> <li>Damashe has not watched the keynote but has listened to everyone talk about it</li> <li>Apple showed features live and uncut, which seems intentional - they want to prove the demos are real</li> <li>Certain AI features require M3 Pro or better on Mac, M4 or better on iPad, and iPhone 17 Pro</li> <li>iOS 26 and 27 compatibility stays the same - if your device runs 26 it will run 27, you just may not get all the local AI capabilities</li> <li>Damashe called the OS unification direction, and he would like you to use the hashtag DamasheWasRight accordingly</li> </ul> <p><strong>iOS 27 Safari Notify</strong></p> <ul> <li>Apple Intelligence can now watch a Safari tab and notify you when something changes</li> <li>Steven Robles used it to get notified when the Unify travel router came back in stock</li> <li>Both Mike and Damashe immediately thought: Ubiquiti restocks</li> </ul> <p><strong>Touchscreen MacBook Speculation</strong></p> <ul> <li>Mark Gurman is pointing toward a high-end OLED touchscreen MacBook Pro at a significant price premium</li> <li>Damashe's alternate theory: what if Apple makes a detachable touchscreen MacBook Neo instead of going ultra-premium</li> <li>The Neo already runs macOS on an A18 Pro chip at $600; a touch-capable detachable version aimed at schools and everyday users could make more sense than a $3,200 pro machine</li> <li>Both agree: a MacBook with cellular would be an instant buy, no questions asked</li> </ul> <p><strong>Are AI Agent Devices Ready to Replace Your Phone?</strong></p> <ul> <li>OpenAI is rumored to be working on a new form factor device built around voice interaction</li> <li>Damashe's argument: not yet, for several reasons - apps, authentication, companies not wanting to be commoditized, and the lack of strong local compute</li> <li>Uber and Amazon are not going to sit still while an agent turns them into a background API</li> <li>The local vs. cloud routing problem is real: you need a local model to manage where requests go, and we are not there on mobile yet</li> <li>Both see 2029-2030 as a realistic window for local compute on personal devices being good enough for most tasks</li> <li>The Plaud Pin has been sitting on a nightstand for months as evidence</li> </ul> <p><strong>Siri and Third-Party Mail</strong></p> <ul> <li>Siri can now surface airline reservations when you call airlines</li> <li>Open question: does it work if your reservation is in Gmail or Outlook instead of Apple Mail</li> </ul> <p><strong>Shortcuts Getting Smarter</strong></p> <ul> <li>The new AI-assisted Shortcuts builder could be the most useful thing in iOS 27 if it actually works</li> <li>Federico Viticci's hope: get Sherlocked properly this time</li> </ul> <hr> <p><strong>Links and Contact</strong></p> <ul> <li>Send feedback: feedback@technicallyworking.show</li> <li>TestFlight beta for Earshot: find Michael on Mastodon at payown@dragonscave.space</li> <li>Damashe on Mastodon: damashe@technically.social</li> <li>Bot: tw@technically.social</li> <li>Support the show: technicallyworking.show, click Support Us</li> </ul> <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/3240cfe1-07d0-4cdc-b340-9d4131f7c84e" rel="nofollow">https://pinecast.com/feedback/technically-working/3240cfe1-07d0-4cdc-b340-9d4131f7c84e</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>

View episode

#166: If You Used a Passkey, Why Are You Asking for a Code?

Passkeys are supposed to make your life easier. So why is Amazon still asking for a six-digit code after you just proved who you are with one? This week, Michael and Damashe dig into what companies are getting right and wrong with passkey implementation, including PayPal's rocky start and how one hardware security key can save you from a bad day on macOS. They also talk about Damashe's new office space, what it actually takes to organize a vending machine operation when you're blind, and why Braille labels still beat pulling out your phone. Plus: the GL.iNet travel router with built-in Tailscale, using Aira to read a Wi-Fi password off the bottom of a router, WWDC predictions including a folding iPhone neither of them is sure they want, and what happens to your whole week when you stop using Todoist. A lot happened. Almost none of it went as planned.

View episode

#165: No Excuses Left for Inaccessible Apps

<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>

View episode

#164: Building the podcast app I actually want

<p>Michael's been frustrated with his current podcast app for months, so he did what any reasonable person would do: opened Claude, wrote a PRD, and started building. Thirty-six versions later, there's a working iOS podcast app with a cross-platform plan, real testers giving feedback, and a list of features pulled straight from what blind podcast listeners actually want.</p> <p>We get into the build process, including why Michael went with a phased approach, the testers who caught things he never would have (player controls missing above the tab bar, search being completely broken, follow buttons not changing to unfollow), and the features people keep asking for like folders and OPML import/export for subsets of subscriptions. Damashe also makes the case for GitHub labels and milestones so feature creep doesn't eat the project alive.</p> <p>From there, things go sideways into Apple's developer experience, which is rough. App Store Connect in Safari with VoiceOver is a mess. Damashe has had to switch to Chrome just to accept terms and conditions. Michael couldn't add testers to a TestFlight group from Safari at all. We hope WWDC has something to say to the wave of vibe coders showing up to Apple's ecosystem this year.</p> <p>We pivot to AI usage in general and make a case for the people who aren't building apps or websites: use these tools to understand things you're not an expert in. Commercial leases, tax code, anything dense and unfamiliar. Feed it the document, ask questions, then verify the answers in a different tool to check for consistency. The AI didn't change Damashe's behavior, by the way. Search has been bad for years. AI just gave him a way around it.</p> <p>Plus: Lyft vs Uber pricing (Lyft was significantly cheaper for both of us this trip), scheduling airport pickups with flight tracking, why Michael won't schedule rides if he can help it, a shoutout to Vijesh at the Hyatt in San Francisco, Damashe needs a new rolling suitcase, and a reminder to Tip Jar subscribers to check your email this week.</p> <h3>Topics</h3> <ul> <li>The vibe-coded podcast app: thirty-six builds, real testers, what's working</li> <li>Why Michael built it: frustration with his current app, wanting cross-platform</li> <li>PRDs as a starting point for AI-assisted projects</li> <li>Tester feedback that mattered: player controls, search, follow buttons, folders, OPML subsets</li> <li>GitHub labels and milestones for managing feature creep</li> <li>App Store Connect accessibility, or the lack of it</li> <li>Practical AI usage for non-developers: leases, tax code, things you don't know</li> <li>Verifying AI answers across different tools</li> <li>Lyft vs Uber: pricing, scheduled pickups, flight tracking</li> <li>Airport tips: leave early, turn off your VPN before you try to use the rideshare app</li> <li>Hotel shoutout: Vijesh at the Hyatt in downtown San Francisco</li> <li>Auphonic as a way listeners can support podcasts</li> <li>Tip Jar subscribers: check your email</li> </ul> <h3>Links</h3> <ul> <li>Technically Working: https://technicallyworking.show</li> <li>Feedback: feedback@technicallyworking.show</li> <li>Tip Jar: https://technicallyworking.show</li> <li>Michael on Mastodon: @payown@dragonscave.space</li> <li>Damashe on Mastodon: @damashe@technically.social</li> <li>Show bot: @tw@technically.social</li> <li>Auphonic: <a href="https://auphonic.com" rel="nofollow">https://auphonic.com</a></li> </ul> <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/b40b48e7-5a95-4a1e-ab4d-c6f884ab7bff" rel="nofollow">https://pinecast.com/feedback/technically-working/b40b48e7-5a95-4a1e-ab4d-c6f884ab7bff</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>

View episode

#163: Our Perspective Launches, Substack Experiments, and Hotel Room Recording

Michael and Damashe catch up from two different locations this week. Damashe is recording from a hotel room in Orlando with the Beta 87A he found at the bottom of his AT Guys backpack. Michael shares an exciting podcast launch and a new writing experiment on Substack. Topics covered in this episode: ACB National Convention 2026 in St. Louis: registration opens May 28 for members, June 4 for non-members. Convention runs July 24 through July 31 in person, with virtual programming starting July 13. Meetup plans: if you'll be in St. Louis between July 25 and 29, send an email and we'll set something up. Send restaurant recommendations too, especially the hole-in-the-wall spots. Marriott vs Hilton: Damashe is collecting Bonvoy points and would pick a Marriott most days. Our Perspective podcast launch: Michael's new show with a friend drops in early June. Two completely blind people talking about how they get through life. Trailer publishes Tuesday, Episode 1 follows shortly after. Search "Our Perspective" wherever you get podcasts. Using Claude to generate the show artwork and learning how to push back when an AI says it can't do something. Substack update: Michael started a Substack at payown.substack.com. AI helps draft posts based on what he's been working on each week. Search Payown on Substack to follow. GitHub featured Michael's video about Builder on LinkedIn to their 6.4 million followers. Pinecast tip: listener.email is a beta feature that gives your podcast a private email address so your personal inbox does not end up in the public podcast database. Use the discount code in the show notes for 40 percent off your first months of Pinecast. bag review update: the zipper finally gave out under heavy packing. Still a solid bag, but worth knowing the limits. Pirate Ship plug for shipping AT Guys demo gear and saving real money on labels. Wingstop talk, dry rub preferences, and the new Citrus Mojo flavor. A handheld 2 meter / 70 centimeter radio that was marketed as fully accessible but is not. At 49 dollars it is still a reasonable buy for what you actually get. Reach out if you want more details. San Francisco meetup: Michael will be in the city May 20 through 23. Reach out if you want to connect. Austin meetup: Damashe will be at NFB Convention July 3 through 8. Stop by the AT Guys booth or email to set up a meetup. Travel app idea: a Lyft vs Uber price comparison app that did not quite work. Still searching for a good one. Backup recording confession: Michael forgot to start Audio Hijack again. Get in touch: Email feedback@technicallyworking.show Mastodon: @payown@dragonscave.space, @damashe@technically.social, @tw@technically.social Hashtag: #TechnicallyWorking Support the show: tip jar link in the show notes. Support Technically Working by contributing to their tip jar: https://tips.pinecast.com/jar/technically-working Find out more at https://technically-working.pinecast.co Send us your feedback online: https://pinecast.com/feedback/technically-working/6ac4263f-0786-437b-a083-5a93e61bb0d5 This podcast is powered by Pinecast. Try Pinecast for free, forever, no credit card required. If you decide to upgrade, use coupon code r-431b7d for 40% off for 4 months, and support Technically Working.

View episode

#162: Already Outgrown: Moving Two Doors Down

Mike's back from a workation and Damashe is recording from a cardboard box in his old office because the new office already isn't big enough. We get into audio app updates, the travel boom arm setup, a new podcast project called Our Perspective, and answer a listener question about starting an email list without breaking the bank. Damashe shares the news that he's already moved to a bigger space, two doors down from the original office, and walks through his automation plans: Home Assistant, Ubiquiti Access for door entry, sensors everywhere, and cameras inside and out. We talk Lucid radios as a possible replacement for giving employees phones, the Perkins Bloom add-on (and why $300 feels steep), Tailscale wins while traveling, and a quick PSA on the recent Linux vulnerabilities. In this episode: Audio Hijack, Loopback, and SoundSource updates Travel boom arm review and mobile recording setup Our Perspective podcast launching early June Listener question: free options for starting an email list (MailChimp, Groups.io, Kit) Teams, SharePoint, and syncing files locally Lucid radio follow-up and deploying them in a business Office move update: twice the space, front-to-back access Home Assistant vs Homey Pro, Ubiquiti Access, and sensor plans Perkins Bloom: $300 to turn your Brailler into a Bluetooth keyboard Throwback to Braille 'n Speak, Braille Lite, and Mountbatten Linux vulnerability PSA: update your machines Tailscale for remote access while traveling Support Technically Working by contributing to their tip jar: https://tips.pinecast.com/jar/technically-working Find out more at https://technically-working.pinecast.co Send us your feedback online: https://pinecast.com/feedback/technically-working/bb830347-99fa-41f1-aaeb-177fa457b8af This podcast is powered by Pinecast. Try Pinecast for free, forever, no credit card required. If you decide to upgrade, use coupon code r-431b7d for 40% off for 4 months, and support Technically Working.

View episode

#161: If I Can't Hear Me, They Can't Hear Me

Technically Working Episode 161: If I Can't Hear Me, They Can't Hear Me Episode 161 comes to you from a hotel room. Michael is on the road with Mallory, recording over hotel Wi-Fi with the DJI wireless mics, and Damashe is at his desk for one last show before move day. What started as a check-in turned into a full walkthrough of portable audio setups, why monitoring yourself matters, and the boom arm that finally solved Damashe's travel mic problem. Damashe is using the new Rode Wireless Micro and walks through his first impressions. The case is barely bigger than an Open Fit case, the receiver is just a USB-C plug with no buttons, the app is accessible (with one quirk around radio buttons that read as dim even when selected), and the noise cancellation is configurable. The one downside is you can't put the windscreen on and close the case. He's leaning toward this over the DJI for portability, though he admits the DJI Mic 2 that Michael uses sounds slightly better. From there, the conversation opens up into a deeper guide on portable recording. They talk through the ATR2500x and Samson Q2U as solid USB/XLR starter mics that work with any operating system, why the Beta 87A is still Damashe's hill to die on for an XLR setup, and the long-running portable audio struggle with mic stands that are technically portable but practically uncomfortable. That problem finally got solved thanks to a tip from Rob Dunwood on the Daily Tech News Show. The Toti mic arm for lightweight mics folds into three sections, clamps onto sloped desk edges, and was on sale for $24. Damashe is impressed. There's a side trip into using your phone as a webcam. Damashe makes the case for Camo over Continuity Camera, mostly because Continuity Camera shows up uninvited and disappears at the worst times. Michael's setup recommendation is an old iPhone with a MagSafe pop socket clipped to the back of your laptop. The episode also covers the cable rule. If you travel with a bag, that bag has its own set of cables and adapters, and you do not borrow from it. Even if a cable in your house dies and you need one right now, do not touch the bag cables until the replacement is already on its way. Damashe learned this in Houston. Plus updates on the move (happening tomorrow), gas prices ($3.29 for Damashe, $5.50 average for Michael, $6.69 in northern California), the bot taking spring break until the new office is set up, and a listener question for the audience: what should the bot be named? Box is on the table but Damashe is not on board. Send your bot name suggestions to feedback@technicallyworking.show or hit them up on Mastodon. Episode Chapter Markers 0:00 - Hotel Wi-Fi, capture portals, and recording on the road 0:25 - MagSafe rumors and why they're not going anywhere 2:09 - Shout out to listeners and a request for App Store reviews 3:41 - Damashe's new Rode Wireless Micro first impressions 5:00 - The case, the receiver, and the accessible app 7:18 - Why monitoring yourself matters 8:19 - Both mics compared side by side 10:01 - Move day prep and storage strategy 11:04 - LaunchBar VoiceOver update and a Mac mute keyboard shortcut problem 12:32 - Gas prices, vending stops, and stay out of California 13:37 - Portable audio setup deep dive begins 16:14 - ATR2500x and Samson Q2U as starter mics 18:21 - The portable mic stand problem 19:57 - The Toti boom arm find 22:21 - The price reveal ($24) 23:13 - Audio interfaces, Zoom recorders, and the H1 XLR 26:12 - The cable bag rule 28:24 - Phones as cameras, Continuity Camera vs Camo 31:46 - Continuity Camera popping up at the worst times 33:00 - Damashe's eBay plans 33:34 - Wrap up and the bot's spring break 35:07 - Name the bot Support Technically Working by contributing to their tip jar: https://tips.pinecast.com/jar/technically-working Find out more at https://technically-working.pinecast.co Send us your feedback online: https://pinecast.com/feedback/technically-working/4402df81-52c8-4b3b-9346-d4bac0297f84 This podcast is powered by Pinecast. Try Pinecast for free, forever, no credit card required. If you decide to upgrade, use coupon code r-431b7d for 40% off for 4 months, and support Technically Working.

View episode

#160: Push to Talk, Pull to Cloud

Technically Working Episode 160: Push to Talk, Pull to Cloud Episode 160 opens with the numbers. Total downloads across the lifetime of the show have hit 33,505, with episode 159 pulling 137 listens and episode 158 sitting at 157 after 14 days. The average is holding around 150 per episode and has been gradually climbing even without any real marketing. Word of mouth and the occasional Mastodon post have done all the work so far. If you want to help, leave a rating in Apple Podcasts or Pocket Casts. From there we get into Apple news. Tim Cook announced he'll be stepping down as CEO, with John Ternus taking over. Michael bought one share of Apple stock and is hoping for the best. Damashe has thoughts on Tim's legacy as an operations-focused leader, where Apple got comfortable, and what services growth has cost the company from a user experience standpoint. Neither of us are financial advisors. Please do not take investment advice from this podcast. Michael also turned a year older this week. Happy belated birthday from the show. Then: AirPods Pro 3. Michael got a pair as an early birthday gift and called Damashe immediately. The volume adjustment from the stem alone was worth the upgrade coming from first-gen. The adaptive listening feature is useful but aggressive, and Comply foam tips are probably going to be necessary for a secure fit. Damashe is sticking with his Pro 2s for now but is more likely to buy than he was before this conversation. Community Builder Tools is going to the cloud. Michael walks through the current setup: developing on Windows, pushing to a Raspberry Pi running Ubuntu, deploying from GitHub, with automated database backups running on a cron job and syncing to Dropbox via rsync. He's now using a web-based version of Builder to manage convention events, which work similarly to the ACB Community schedule across multiple Zoom accounts. A training is happening the next day. More details coming soon. Waymo. Michael is flying into San Francisco on May 20th for the GitHub hackathon and plans to take a Waymo just for the experience. Damashe is less enthusiastic than he was ten years ago, not because the tech isn't impressive, but because he's seen enough things break to have questions. The power outage in San Francisco that left Waymos sitting in the road is a real example. The conversation goes wide from there: onboard compute versus network dependency, insurance liability, the limits of LLMs, rural connectivity, and whether the companies working on this are solving the right problems in a meaningful way. Damashe would still take one in Austin this summer. He just has more conditions attached. The POC radio. Michael ordered the Lucid Budget Radio, a push-to-talk over cellular device that costs $99 with cellular plans starting at $20 for a year. It does not make the Nextel chirp sound, which is a disappointment. It does work across AT&amp;T, T-Mobile, and Verizon via a smart SIM. It's accessible — the manufacturer responded to a blind user's feedback within three weeks with a working solution — and Michael is already thinking about using it for convention communications. Damashe also covers a dual-SIM router he picked up for his work van, how he's using a physical eSIM card to load up to eight profiles, and a new office space he's moving into next weekend. He's looking for suggestions on door access solutions, a security system, and sound panels. Send ideas to feedback@technicallyworking.show. Todoist check-in: Michael is at 7,425 completed tasks and sitting at Grand Master status with 15,000 points to go until Enlightened. His current streak is seven days after breaking it. Damashe broke his for the same reason: things got done, the app didn't get opened. Links and Resources Technically Working: technicallyworking.show Send feedback: feedback@technicallyworking.show Lucid Budget Radio: simpleptt.com/product-page/the-2026-lucid-budget-radio Comply foam tips for AirPods Pro 3 (get the version made for the 3, the connector is different from the 2) Tip jar and supporter info: technicallyworking.show Michael on Mastodon: @payown@dragonscave.space Damashe on Mastodon: @damashe@technically.social Bot: @tw@technically.social Hashtag: #TechnicallyWorking (capitalize the T and W so NVDA reads it right) Ready for social posts when you are. Support Technically Working by contributing to their tip jar: https://tips.pinecast.com/jar/technically-working Find out more at https://technically-working.pinecast.co Send us your feedback online: https://pinecast.com/feedback/technically-working/c4281865-99ac-49ce-b773-398c47afece8 This podcast is powered by Pinecast. Try Pinecast for free, forever, no credit card required. If you decide to upgrade, use coupon code r-431b7d for 40% off for 4 months, and support Technically Working.

View episode

#159: Zoom Bloat, NVDA Wins, and the Great BlindShell Retreat

TW 159: Zoom Bloat, NVDA Wins, and the Great BlindShell Retreat Mike and Damashe catch up on a Wednesday (weird, we know). Damashe wraps up his BlindShell experiment after about three weeks, shares news about a new commercial office space, and both hosts get into why Zoom keeps bolting on features nobody asked for. Mike talks about his growing comfort with NVDA, useful add-ons he's found, and what it took to make the switch feel natural. Plus vibe-coded tools, Stream Deck planning, a great file upload tip, and the state of LaunchBar in 2026. In this episode: • Damashe's BlindShell experiment wraps up (and why) • Missing SD cards and the Raspberry Pi graveyard • Damashe has office space news • Zoom Pro, Google Meet, and the "why am I paying for this" question • Apple, Spotify, and platform owners competing with their own marketplace • Android vs iOS, and the lies people have been telling for 15 years • Why Gmail on Android is still painful • Mike's move to NVDA: what helped, what tripped him up • The Eloquence voice that made everything click • Caps Lock as a VoiceOver modifier and the shortcuts it breaks • Stream Deck planning, vibe-coded utilities, and Farrago timing • Rogue Amoeba, AppleScript, and why it matters • New LaunchBar 6.23 with VoiceOver improvements • VOCR 3.0 beta 2 is broken on current macOS (heads up) • A killer file upload tip: paste from Finder directly into upload dialogs • Mac/iOS developers: explain why your app needs Bluetooth and network access Mentioned in this episode: • NVDA add-ons: Speech History, Virtual Window, shortcut utility • AT Guys Eloquence SAPI 5 voices • LaunchBar 6.23 • VOCR 3.0 beta 2 • Farrago (Rogue Amoeba) • BlindShell • Parallels for macOS • Lenovo ThinkPad X1 Carbon Guess the mic: Damashe is using a different setup this week. Can you identify the microphone? Bonus points for the interface. Send your guesses to feedback@technicallyworking.show. Support the show: Tip jar subscriptions and one-time tips keep the lights on. Thanks to subscriber number one, still going strong. Connect: • Email: feedback@technicallyworking.show • Damashe: @ damashe@technically.social • Mike: @ payown@dragonscave.space • Bot: @ tw@technically.social • Hashtag: #TechnicallyWorking Support Technically Working by contributing to their tip jar: https://tips.pinecast.com/jar/technically-working Find out more at https://technically-working.pinecast.co Send us your feedback online: https://pinecast.com/feedback/technically-working/19f4814d-749f-4948-8879-a7e93c6cabec This podcast is powered by Pinecast. Try Pinecast for free, forever, no credit card required. If you decide to upgrade, use coupon code r-431b7d for 40% off for 4 months, and support Technically Working.

View episode

#158: Push to Talk

Michael's audio is doubled and nobody knows why. What starts as a deep dive into Audio Hijack routing, virtual devices, and a suspicious SoundSource redirect turns into a full troubleshooting session that anyone running a complex audio setup will relate to. Damashe shows up with a new Earthworks Ethos microphone and the two get into mic comparisons, boom arm weight limits, and whether the RE-20 is worth the investment. From there, the conversation shifts to coding workflows. Michael shares progress on a Flask project built with Claude, and Damashe walks through Git branching, atomic deployments, and what happens when your LLM decides to push to production without permission. Both talk about using Claude, Gemini, and GPT for different tasks, and Damashe shares early impressions of the Claude desktop app. Then Michael highlights an affordable tri-band ham radio with braille on the keypad and built-in voice output, and gives a quick rundown of how ham radio works, why it matters for emergency communication, and how linked repeaters let him talk to someone near Seattle from a handheld in Coos Bay. The two wrap up discussing Artemis 2's laser communications, the case for alternative communication networks, and yes, Outlook failing in space. feedback@technicallyworking.show | Mastodon: @tw@technically.social | #TechnicallyWorking Support Technically Working by contributing to their tip jar: https://tips.pinecast.com/jar/technically-working Find out more at https://technically-working.pinecast.co Send us your feedback online: https://pinecast.com/feedback/technically-working/0246b25b-4842-4bcd-9520-3c5916f59e27 This podcast is powered by Pinecast. Try Pinecast for free, forever, no credit card required. If you decide to upgrade, use coupon code r-431b7d for 40% off for 4 months, and support Technically Working.

View episode

#157: This Is Fine, Everything Is Fine

Episode 157 opens with a VoiceOver volume bug on Michael's Mac that resets to 100 percent every time he command tabs. Damashe suggests the nuclear option: reset your VoiceOver settings. Back them up first. From there, Damashe gets into his Blindshell Classic 3 experiment. He's been using it as his actual work phone, which means carrying it when he leaves the house, taking calls on it, and finding out what it can and cannot do when theory meets reality. The short version: phone calls work fine, T9 input is usable with a tip Michael drops about the down arrow shortcut, Be My Eyes camera quality genuinely surprised him, and the dual SIM situation does not work. At all. Whatever is in SIM slot 2 does nothing. Switch the cards around and the other one works fine in slot 1. Damashe has a hypothesis. Blindshell, he is sending you this episode. He also paired a Bluetooth keyboard to the Blindshell, got his Meta Ray-Bans connected, and found out phone calls come through the glasses just fine. Screen reader audio does not, at least not by default. That test is still pending. A few other Blindshell notes worth knowing: there is no company name field in contacts, apps access your microphone without asking permission, and the lock screen keypad instructions are printed right on the lock screen, which is not exactly a security feature. Damashe is not bashing the phone. He is just reporting what he found. There is also a broader point he makes about what Blindshell missed. The community already named the product. They call it the shell phone. Blindshell should have listened to that, leaned into it, and used it to market the device beyond just the blind community. A well designed keypad phone with accessible Android underneath could appeal to a lot of people. Instead the branding closes the door before anyone outside the community even considers it. The Clix Communicator gets a mention here as a device that might actually do this right, if it ever ships. Then there is Graphene OS. Damashe has it running on a separate Android device, kept completely isolated, for reasons he will describe only as just in case. If that makes sense to you, run with it. If not, everything is fine. Messaging apps come up next. Damashe breaks down Signal versus WhatsApp in plain terms, including a genuinely useful explanation of metadata using a letter in the mail as the analogy. He also wants Signal to add device linking because it would make recommending it a lot easier. Michael mentions an ACB affiliate mailing list that uses Signal groups, which he did not know was a thing. Michael's OpenClaw setup gets a proper rundown. He is running the assistant named K on his Raspberry Pi, connected through Telegram, using three models depending on the task: OpenRouter free for simple back and forth, GPT-5.4 mini for emails and scheduling, and GPT-5.4 for deeper content work. He burned through $35 in a weekend before the API cut him off at negative two cents. The system now sends him a daily recap at 7:30 PM, manages its own memory, and archives previous days into markdown files. He has not set up the 1Password skill yet but it is on the list. Damashe spent the entire week not using AI and felt strange about it. Not unproductive, just strange. He also has thoughts about the Claude code leak and whether anyone is actually reviewing what gets pushed. He does not have answers. Neither does Michael. Proton Workspace gets a quick mention as a direct competitor to Google Workspace and Microsoft 365. If you use Proton Mail already and want to talk about it on the show, email them. The Keychron folding keyboard arrived. Damashe opened it, looked at it, and said it is not what he expected. He has not paired it to anything yet. Full report coming. Episode closes with a shout out to tip jar subscriber number six, whoever that is. Topics covered: VoiceOver volume reset bug and how to back up your VoiceOver settings Blindshell Classic 3 as a daily work phone: what works and what does not Dual SIM on the Blindshell Classic 3: broken, probably by design T9 input tip: down arrow shortcut to speed up letter entry Be My Eyes camera quality on the Blindshell Meta Ray-Bans paired to the Blindshell: calls yes, screen reader no Blindshell's missed opportunity: the shell phone name and broader market appeal Clix Communicator as a phone that might get this right Graphene OS: no further questions Signal vs WhatsApp: features, metadata, and why Damashe is on WhatsApp now Metadata explained with a mail analogy Michael's OpenClaw setup: three models, one budget, daily recaps GPT-5.4 mini, GPT-5.4, and burning through $35 in a weekend The Claude code leak and vibe coding concerns Proton Workspace as a Google and Microsoft competitor Keychron folding keyboard: first impressions, not great Send feedback: feedback@technicallyworking.show Support the show: technicallyworking.show Follow on Mastodon: Michael: @payown@dragonscave.space Damashe: @damashe@technically.social Show bot: @tw@technically.social Support Technically Working by contributing to their tip jar: https://tips.pinecast.com/jar/technically-working Find out more at https://technically-working.pinecast.co Send us your feedback online: https://pinecast.com/feedback/technically-working/e519280c-f74a-4875-be3b-2dffe2b22ed0 This podcast is powered by Pinecast. Try Pinecast for free, forever, no credit card required. If you decide to upgrade, use coupon code r-431b7d for 40% off for 4 months, and support Technically Working.

View episode

#156: Streaks, Macs, and Smart Locks

Episode 156 opens with some breaking Apple news: the Mac Pro is officially dead. Damashe breaks down why that decision probably came down to Apple Silicon's unified memory architecture and what it means for professionals who relied on the Mac Pro's expandability. We trace the full arc from the original cheese grater to the ill-fated trash can and back again, and talk about why the Mac Studio is likely where Apple thinks that story ends. From there, we get into recording setups. Michael is back in the garage with a rug, a mic stand from Damashe, and the Vocaster running into an OWC dock. Damashe is on the Zoom P4 Next, and he breaks down how that compares to the Vocaster for anyone thinking about a step up, including what he likes, what he doesn't, and why locking XLR ports matter more than you'd think. We also share a few honest tips for improving your recording environment without buying new gear. Rugs, soft surfaces, and where you point your microphone matter more than most people realize. Then: the Todoist situation. Michael came home from CSUN with a 114-day streak that didn't survive the trip. He explains what happened, how he's building back, and what his 7,000-plus completed tasks say about how he actually uses the app. Damashe broke his streak around the same time for a much more relatable reason. The back half of the episode is dedicated to a question from Chad, who just closed on his first house. Congratulations, Chad. He wanted follow-up on cameras and smart locks, so we go wide first: start with your ecosystem, know your priorities around cloud storage versus local recording, and think about who else in your home is going to be using this stuff. Damashe is using Reolink cameras with a network video recorder for fully local storage, a Level Lock Plus for his front door, and Aqara devices throughout the house. Michael is running Eufy cameras through HomeKit Secure Video and has had mixed results with the Level Bolt. Both of us agree: Aqara makes solid, affordable hardware, and if you own your home, power-over-ethernet cameras are worth planning for even if you can't run the cable today. We also make a case for water leak sensors, which are less exciting than smart lights but probably more important once you own the place. We close with a tease of something new coming likely by end of April. If you follow Michael on Mastodon, you'll probably hear about it there first. Topics covered: Apple kills the Mac Pro: what it means and why it probably happened Mac Pro history: cheese grater, trash can, 2019 refresh, and the M2 Ultra version that didn't save it Apple Silicon unified memory and why it complicates expandability Recording environment tips: rugs, soft surfaces, closets, and mic placement Vocaster vs Zoom P4 Next: comparing two portable interfaces Shure Beta 87A and why condenser vs dynamic matters for your space Todoist streaks, gamification, and what 7,000 completed tasks looks like Smart home ecosystem advice: start with what you're already in Cameras: Reolink, Eufy, Ring (why Damashe won't recommend it), POE vs battery HomeKit Secure Video and what it means for local vs cloud storage Smart locks: Level Lock, Aqara retrofit deadbolts, U-Bolt (avoid) Water leak sensors and why they matter if you own your home New show incoming Send feedback: feedback@technicallyworking.show Support the show: technicallyworking.show (Support Us link) Follow on Mastodon: Michael: @payown@dragonscave.space Damashe: @damashe@technically.social Show bot: @tw@technically.social Support Technically Working by contributing to their tip jar: https://tips.pinecast.com/jar/technically-working Find out more at https://technically-working.pinecast.co Send us your feedback online: https://pinecast.com/feedback/technically-working/4ecaf69e-1b6b-459e-85eb-66b367628ae9 Check out our podcast host, Pinecast. Start your own podcast for free with no credit card required. If you decide to upgrade, use coupon code r-431b7d for 40% off for 4 months, and support Technically Working.

View episode

#155: Walking In With Confidence: CSUN, Braille Displays, and Server Shenanigans

Damashe and Michael are back for episode 155 of Technically Working, and this one is packed. They start by addressing the episode 153 publishing mishap where Michael's audio track was accidentally left out of the Auphonic template, leaving listeners with a two-person conversation missing one of the people. They break down exactly what happened, how their podcast production workflow contributed to the issue, and what they're changing in their Dropbox and Auphonic setup to prevent it from happening again. Next up, the technically.social Mastodon instance went offline after a billing issue with masto.host. Damashe walks through the full story of how a separated email alias caused him to miss payment failure notifications, how the hosting provider cancelled the account with no option to reactivate, and how he rebuilt the Mastodon server on CloudRun. The Technically Working bot is back online, refederated, and ready for followers at @tw@technically.social. Damashe is recording on the Shure Beta 87A, and both hosts take time to explain why this super cardioid condenser microphone is their top recommendation for podcasters and content creators looking to upgrade to XLR. They cover the mic's pickup pattern, durability, price point (typically around $200 on sale), and how it compares to alternatives like the Samson Q2U, the Audio-Technica ATR 2100X, and a brand new Audio-Technica 2500X that neither host has tested. They also discuss the Focusrite Vocaster One and Vocaster Two as affordable audio interfaces with phantom power for anyone building a home podcast studio setup. Michael brings a detailed CSUN 2026 recap from Anaheim. His hands-on impressions cover a wide range of assistive technology and accessibility products including the Dot Pad X multi-line braille display from AT Guys, the Mnemonic portable Bluetooth braille labeler that embosses onto DYMO and metal tape from a phone app, and the Cadence, a 48-cell refreshable braille tablet with four lines of 12 cells, an impressive refresh rate, and the ability to daisy-chain up to four units together. Michael also visited the DOT and LG booth where they demonstrated a fully accessible self-checkout kiosk with speech output, headphone jack, and a 12-cell braille display built into the unit. LG showcased accessible home appliances including a washer, dryer, refrigerator, and dishwasher with braille labels, adaptive features for users with upper body limitations, and the ThinkQ smart home hub with voice control. Samsung's accessibility sticker program for appliances also gets a mention. On the braille display side, the episode covers the Thinkerbell Labs 40-cell braille display running Linux and targeting a $1,200 price point, the Orbit Flow (a USB-only 40-cell aluminum braille display, and the Orbit Strata with combined braille and speech output. Michael also shares his experience with the Orbit Optima and discusses the differences between Piezo and True Braille cell technology. Damashe and Michael discuss braille on business cards, why QR codes linking to vCard contact information should be the standard at conferences, and the challenge of scanning business cards accessibly. Damashe puts out a call to listeners for accessible business card scanning app recommendations. Damashe introduces changedetection.io, a self-hosted website monitoring tool he installed on CloudRun to track product pages for stock changes. He set it up to watch for Ubiquiti mobile routers that were out of stock, got a Pushover notification when they came back, and grabbed them before they sold out again. He explains how he's planning on using the routers with SIM cards to provide cellular Wi-Fi for security cameras at his rest area vending locations, and discusses the tradeoffs between rugged outdoor-rated routers and cheaper alternatives with 3D-printed enclosures. The episode wraps with a podcast download stats update: 31,092 total downloads, 409 in the last seven days, and 142 downloads for episode 154 in just three days. Damashe teases the new Technically Working website, confirms the URL structure will support direct episode links like technicallyworking.show/155, and shares plans to expand the show's social media presence to Blue Sky. They celebrate three years of weekly podcast publishing with no missed episodes and welcome new listeners who discovered the show at CSUN. Links and resources: Technically Working: technicallyworking.show Send feedback: feedback@technicallyworking.show AT Guys Braille Apps for Dot Pad: braille.atguys.com changedetection.io Support the show: technicallyworking.show (tip jar link on podcast page) Mastodon bot: @tw@technically.social Damashe on Mastodon: @damashe@technically.social Michael on Mastodon: @payown@dragonscave.space Hashtag: #TechnicallyWorking Support Technically Working by contributing to their tip jar: https://tips.pinecast.com/jar/technically-working Find out more at https://technically-working.pinecast.co Send us your feedback online: https://pinecast.com/feedback/technically-working/6662e615-658f-4b52-a8b1-70dc332c802e Check out our podcast host, Pinecast. Start your own podcast for free with no credit card required. If you decide to upgrade, use coupon code r-431b7d for 40% off for 4 months, and support Technically Working.

View episode

#154: Backing Up Right, The Vocaster Deep Dive, and How We Actually Got Started with AI

Michael and Damashe open with a hard-learned lesson about database backups after an update to the Builder tool wipes fresh data, and why separating your database from your app files matters more than you think. From there, the episode shifts into the next chapter of the audio gear mini-series: a thorough look at the Focusrite Vocaster 1 and 2. The hosts cover what makes these interfaces stand out for screen reader users, including the accessible Vocaster Hub software, auto gain, the bidirectional aux port, Bluetooth on the Vocaster 2, and one major trade-off you need to know about before you unplug your laptop. Listener feedback from Chris leads to a candid conversation about how Michael and Damashe each got started using AI tools and writing code. Michael traces his path from a 2024 Python class through GitHub Copilot to building accessible desktop apps with PySide6. Damashe reflects on using LLMs to debug server logs, review code, and solve real problems without spending hours in Stack Overflow. Together they make the case for starting simple, finding a problem worth solving, and not letting the hype push you somewhere you're not ready to go. The episode wraps with thoughts on the Samsung event, Apple's AI missteps, Google I/O timing, and the launch of an AI-powered Mastodon bot for the show. Send feedback to feedback@technicallyworking.show. Support the show through TipJar . Find Michael on Mastodon at @payown@dragonscave.space and Damashe at @damashe@Technically.social. Follow the show bot at @tw@technically.social using #TechnicallyWorking. Support Technically Working by contributing to their tip jar: https://tips.pinecast.com/jar/technically-working Find out more at https://technically-working.pinecast.co Send us your feedback online: https://pinecast.com/feedback/technically-working/45edf9b5-ad76-4133-80d9-1bd6fe08c46a Check out our podcast host, Pinecast. Start your own podcast for free with no credit card required. If you decide to upgrade, use coupon code r-431b7d for 40% off for 4 months, and support Technically Working.

View episode

#153: Feeling It: A Deep Dive into Multi-Line Braille Displays

Episode Summary This week, Michael and Damashe are joined by Chris, an assistive technology professional who is one of the few people in the accessibility community using both of the major multi-line Braille displays currently on the market: the APH Monarch and the DotPad X. The conversation covers what these devices do, how they compare, and how Chris is using them in her teaching and personal life in ways that go well beyond what most people have imagined. The episode also gets into AI tools for everyday work, recording gear, iPhone versus Android as a daily driver, and some genuinely great audience feedback about the show. Support Technically Working by contributing to their tip jar: https://tips.pinecast.com/jar/technically-working Find out more at https://technically-working.pinecast.co Send us your feedback online: https://pinecast.com/feedback/technically-working/2f66eef8-9020-4d1b-b95f-6726125b8766 Check out our podcast host, Pinecast. Start your own podcast for free with no credit card required. If you decide to upgrade, use coupon code r-431b7d for 40% off for 4 months, and support Technically Working.

View episode

#152: Mics, Passwords, and Postmark: Getting Your Tech Stack Right

2. Show Notes Episode 152 - Technically Working Michael and Damashe are back with a packed episode covering gear, passwords, transactional email, and how to get the most out of your AI tools. Plus, Mike hits a milestone and there's a guest teased for next week. Topics covered: Mic Talk (Mini-Series Continues) Damashe is back on the Audio-Technica ATR 2005 over USB, and explains why this style of mic remains a solid starter or travel option. The ATR 2100x and Samson Q2U both offer USB and XLR connections, making them flexible picks for new podcasters or anyone who wants a good-sounding mic for Zoom calls. Neither is recommended for run-and-gun situations, but both shine at a desk. Password Managers One Password recently raised prices for individual and family accounts. Michael's annual plan jumped from $35.88 to $47.88. That sparked a longer conversation about where people's passwords actually end up, spread across multiple apps and browsers. The guys walk through several options, including 1Password, Bitwarden (free tier available, $10 per year paid), ProtonPass, Apple Passwords, and KeePass. Apple Passwords works well for people deep in the Apple ecosystem, but the sharing and permission structure has limitations. ProtonPass got a positive accessibility mention from a listener. If you're cross-platform, 1Password and Bitwarden are still the strongest picks. Tip from a listener named Scout: ProtonPass is accessible. AI Tools and How to Use Them Well Both hosts have been using Claude heavily for scripting, Google Apps Script, and Python work. Key prompting tip: don't lead the AI with your assumptions. Instead of asking if a specific approach will work, describe what you want to accomplish and ask for options. Then interrogate the answer. Even if you don't know the subject well, asking "are you sure?" causes the model to recheck itself. This tip came from Matt Geek Gal and both hosts have been applying it regularly. Postmark: Transactional Email Made Approachable Damashe has been setting up Postmark for transactional email and invited Michael to explore it together. Key concepts broken down: servers in Postmark are essentially folders, not web servers. You verify your domain by adding two DNS records, a DKIM record and a return path record. Postmark puts new accounts in a sandbox that limits sending to verified addresses only, protecting their deliverability reputation. Getting out of the sandbox was quick, with a human review and approval happening overnight. Postmark separates transactional and bulk email into streams, and you can add additional streams for testing or staging environments. Inbound email routing is also supported. For 10,000 emails per month, pricing runs around $18 to $20. Siri and ChatGPT Siri's integration with ChatGPT has made both hosts more willing to ask quick questions by voice. Answers now come back summarized rather than handing off to a browser link. Still not perfect, especially with home automation commands, but noticeably better than two years ago. Milestone As of this recording, Michael has been with ACB for one year. Damashe points out he's automated himself into more work, not less, which is exactly the kind of employee you want to keep. Listener News A new listener was recruited by Michael while on a phone call. Shoutout to Chris for pioneering the one-time Tip Jar option. Another tip came in since then. Monthly subscribers are appreciated too. Next Week A guest is joining the show. No hints were dropped, but Damashe will be on different gear. Links and Resources Postmark: postmark.com Bitwarden: bitwarden.com 1Password: 1password.com ProtonPass: proton.me/pass Samson Q2U mic Audio-Technica ATR 2100x Subscribe on your favorite podcast app and search Technically Working Follow the hosts: Michael: @payown@dragonscave.space Damashe: @damashe@technically.social Show bot: @tw@technically.social Hashtag: #TechnicallyWorking (capitalize the T and W on Mastodon) Support Technically Working by contributing to their tip jar: https://tips.pinecast.com/jar/technically-working Find out more at https://technically-working.pinecast.co Send us your feedback online: https://pinecast.com/feedback/technically-working/1576a4b8-1626-4323-bbd9-a22f3c8a14f7 Check out our podcast host, Pinecast. Start your own podcast for free with no credit card required. If you decide to upgrade, use coupon code r-431b7d for 40% off for 4 months, and support Technically Working.

View episode

#151: Mic Check: Video Mics, Audio Interfaces, and Vibe Coding Wins

This week, Damashe and Michael dive into a hands-on comparison of the DJI Mic Mini and DJI Mic 2, talking through what makes these wireless lapel mics shine for video content and where they fall short for audio-only podcasting. You'll hear Damashe's mic in action throughout the episode. Damashe kicks off a new series where he'll rotate through several audio interfaces, using the same Beta 87A microphone as a constant, so listeners can hear real differences and eventually land on a recommended setup alongside Michael. This episode features the DJI Mic Mini. Future episodes will feature the Vocaster One, the Zoom H5 Studio, the Soundcraft MTK 12, and others. Damashe also reveals that his go-to recording microphone has been the Earthworks Ethos condenser, and explains why he picked it over the Beta 87A as his studio mic while keeping the 87A as a travel option. For most listeners, his current recommendation for a podcasting mic is the Beta 87A, typically found between $200 and $215. On the tech side, the guys talk about vibe coding updates, including how Michael used Claude in planning mode to shrink his Builder app's load time from around 30 seconds down to about two seconds by switching to lazy module loading. They also discuss IFTTT webhooks, Pushover notifications, and how Damashe built a system to get push alerts whenever the podcast gets a new tip or reaches a download milestone. Other topics include Bluetooth auto-connect annoyances and how to fix them on Mac, the Project Hail Mary movie coming to Prime, and a quick update on Damashe's MacBook Pro and iPad mini repair situation with Apple. Marketing Plan Notes (not written out yet, just the approach): When you're ready to build the marketing content, the main angles to plan around are: The audio interface series as an ongoing hook, giving people a reason to tune in each week The vibe coding / Claude planning mode moment as a standalone clip or short The DJI Mic Mini review content, which plays well for video creator and accessibility audiences The IFTTT + Pushover automation walkthrough as a practical tip post or thread Listener shoutouts and the tip jar mention as community engagement touchpoints Let me know when you want to build that out. Support Technically Working by contributing to their tip jar: https://tips.pinecast.com/jar/technically-working Find out more at https://technically-working.pinecast.co Send us your feedback online: https://pinecast.com/feedback/technically-working/9b72d4fb-7c95-4540-b721-aaafad285f0a Check out our podcast host, Pinecast. Start your own podcast for free with no credit card required. If you decide to upgrade, use coupon code r-431b7d for 40% off for 4 months, and support Technically Working.

View episode

#150: Fixing VoiceOver Menus, Audio Hijack Deep Dives, and Our Social Media Marketing Strategy

Episode 150 - Published February 15, 2026 Michael and Damashe celebrate episode 150 with a technical troubleshooting session that turns into a masterclass on VoiceOver settings, Audio Hijack experimentation, and podcast marketing strategies. In This Episode: VoiceOver Menu Fix (Critical for Mac Users) The solution to broken menu bar navigation in VoiceOver Why "Mouse pointer follows VoiceOver cursor" causes problems How to configure VoiceOver Utility settings properly When mouse tracking is useful vs. problematic Audio Hijack Exploration Real-time compression testing and audio processing Setting up test sessions to experiment with effects The difference between recording with effects vs. applying post-production Tips for session documentation and organization Hardware Updates Damashe's DJI Mic Mini purchase and setup ($80 with charging case) Insta360 Flow 2 Pro gimbal for iPhone video content Loupedeck controller for podcasting workflows Apple repair adventures with MacBook Pro and iPad Mini 6 Podcast Marketing Strategy Using Claude AI to identify clip-worthy moments from transcripts Creating video shorts with AI-generated visuals Buffer integration for multi-platform scheduling Open Claw (ClaudBot) automation coming soon YouTube growth plans and content strategy Shout Outs Christopher Sims - Thank you for the Tip Jar support! All our Tip Jar subscribers - You make this show possible Mentioned Resources Audio Hijack by Rogue Amoeba DJI Mic Mini (2 transmitters + receiver + charging case) Insta360 Flow 2 Pro gimbal Buffer for social media scheduling VoiceOver Utility settings Contact &amp; Support Email: feedback@technicallyworking.show Mastodon: Michael: @payown@dragonscave.space Damashe: @damashe@technically.social Bot: @TW@technically.social Hashtag: #TechnicallyWorking (please capitalize the T, T, and W) Support the show: https://tips.pinecast.com/jar/technically-working Support Technically Working by contributing to their tip jar: https://tips.pinecast.com/jar/technically-working Find out more at https://technically-working.pinecast.co Send us your feedback online: https://pinecast.com/feedback/technically-working/2134cc23-ed56-489d-a590-a3019dc674a0 Check out our podcast host, Pinecast. Start your own podcast for free with no credit card required. If you decide to upgrade, use coupon code r-431b7d for 40% off for 4 months, and support Technically Working.

View episode

#149: Hiring Claude as a $100 Virtual Assistant

Episode 149: Hiring Claude as a $100 Virtual Assistant Episode Description This week, Damashe considers canceling his Claude subscription... only to immediately sign up for a more expensive plan to hire Claude as his virtual assistant. Meanwhile, Michael tackles a Stream Deck accessibility project with help from Claude Code, and the guys make potentially dangerous plans to unleash OpenClaw on their Mastodon bot. Plus: RSS reader workflows, notification rage-quitting, Bitcoin regrets, and why good help really is hard to find (whether human or AI). Topics Discussed AI Assistants &amp; Claude (2:00) Damashe's plan to use Claude as a $100/month virtual assistant The $50 API credit offer (expires February 16th!) Why AI hasn't taken jobs... yet Claude Code living in the terminal Stream Deck Accessibility Project (15:00) Making Stream Deck usable for blind users on Windows and Mac The power of profiles and context-switching Integration possibilities with Bunches, shortcuts, and automation RSS Readers &amp; Workflows (6:00) Net News Wire, Liray, and the eternal search for the perfect feed reader Why preview mode matters The Verge's Twitter-on-their-website approach OpenClaw Plans (1:07:00) Security concerns and Leo's removal The bot that got itself a phone number and called its owner Plans to unleash it on the @TW Mastodon bot Building a kill switch (before the bot reads this transcript) Good Help is Hard to Find (30:00) Why reliable contractors are priceless The 90-day test for employees who think the job is easy Michael's subcontractor success story Also Discussed Cash App notification rage-quitting Uber's marketing message problem Bitcoin: "I would have sold it at $2,000" Home Assistant Yellow module installation anxiety Raspberry Pi 5 (16GB) for sale! Links &amp; Resources Follow the bot: @TW@technically.social (before OpenClaw takes over) Claude $50 credit: Redeem in settings before Feb 16th Harper's blog: Early Claude Code adopter mentioned on TWiT Net News Wire: Open source RSS reader PineCast referral: 50% off first 4 months (link in show notes) Show Stats Total downloads: 29,312 (just 688 away from 30K!) Episode 148: 45 downloads Episode 147: 154 downloads Help us grow: Subscribe a friend! Contact Email: feedback@technicallyworking.show Michael: @Payown@dragonscave.space Damashe: @Damashe@technically.social Use #TechnicallyWorking to join the conversation Support the show at technicallyworking.show/tipjar Episode 149 • Runtime: ~1:13:00 Support Technically Working by contributing to their tip jar: https://tips.pinecast.com/jar/technically-working Find out more at https://technically-working.pinecast.co Send us your feedback online: https://pinecast.com/feedback/technically-working/05cb5ac5-15af-4793-b9dc-33816faea911 Check out our podcast host, Pinecast. Start your own podcast for free with no credit card required. If you decide to upgrade, use coupon code r-431b7d for 40% off for 4 months, and support Technically Working.

View episode

#148: Cookie, Claude Bot, and the “Run It on a Pi” Rule

Show Notes This episode covers a wide range of real-world tech experiments, AI tools, and the line between helpful automation and “maybe don’t give that full access yet.” We start with money talk (not advice). Damashe shares that he finally opened a Fidelity account and bought his first stock, while Michael talks about using watch lists and trade notifications. They also explore how accessible investing apps are getting, including audio charts and VoiceOver support, plus where accessibility still falls short. Claude Bot and AI with real power A big chunk of the episode focuses on Claude Bot, an open-source tool that lets you interact with an AI through messaging apps like Signal, WhatsApp, and more. The idea of giving an AI access to your computer is exciting… and a little terrifying. This leads to the show’s unofficial safety rule: &gt; If an AI tool can take actions on your system, run it on a Raspberry Pi or other isolated setup first. They break down risks like prompt injection, why connecting AI to email and calendars can be dangerous, and why curiosity should always be paired with caution. AI for everyday life: meet Cookie On the more practical side, Michael shares a cooking app called Cookie. It reads recipes out loud, lets you ask questions like “What’s the next step?” and even suggests ingredient substitutions. It was not originally built for accessibility, but turned out to be incredibly useful for blind cooks. A great example of AI being used in a focused, practical way. Smarter notes and personal workflows Damashe talks about using AI with DevonThink to automatically organize documents, and why he’s eyeing Drafts with new automation features. The goal: speak a quick note and have it turn into structured data, lists, or tasks without manual sorting. Social apps, open source, and platform politics There’s also discussion about: A new accessible Mastodon and Bluesky client Mastodon instances blocking apps built with AI assistance The tradeoffs of open platforms where each server sets its own rules Linux curiosity returns More blind tech users are experimenting with Linux on the desktop again. The hosts are curious what’s improved, especially with screen readers, and ask listeners to share their experiences. And yes… Todoist check-ins They wrap with progress (and setbacks) on staying consistent with task tracking. Support Technically Working by contributing to their tip jar: https://tips.pinecast.com/jar/technically-working Find out more at https://technically-working.pinecast.co Send us your feedback online: https://pinecast.com/feedback/technically-working/887fda25-0695-49dd-9853-1586cd71fe1c Check out our podcast host, Pinecast. Start your own podcast for free with no credit card required. If you decide to upgrade, use coupon code r-431b7d for 40% off for 4 months, and support Technically Working.

View episode

#147: AI Everywhere: Smart Homes, Smarter Servers, and Dumber Customer Service

This week starts nerdy and only gets nerdier in the best way. Michael and Damashe bounce from Apple rumors to AI customer service fails, with plenty of practical tech talk in between. 🤖 Apple, AI, and the Future of Siri We dig into the rumors around Apple’s AI direction and what it might really mean for Siri, a possible Home hub device, and Apple’s partnership with Google’s AI models. Are we finally close to a version of Siri that feels truly useful? We share what we’re hopeful about and what still feels like vaporware. 🧠 General AI vs. Specialized AI From Perplexity to Amazon Q, we talk about the shift from “AI that tries to know everything” to smaller models trained for specific tasks. Why focused AI might actually be more helpful and less likely to make things up. ☁️ Amazon Q and Learning AWS the Easy Way Michael has been setting up Amazon SES and got a firsthand look at Amazon’s built-in AI assistant, Q. We talk about how tools like this can make complex platforms like AWS more approachable, especially when you can ask follow-up questions in plain language instead of digging through documentation alone. 📧 Why Michael Is Switching to Amazon SES Michael walks through why he’s moving WordPress email over to Amazon SES. The big takeaway: sending email at scale can be shockingly inexpensive if you’re willing to do a little setup yourself. We also cover SPF records, sending domains, and a few beginner tips to avoid common mistakes. 🏠 Smart Home Wins and Headaches From smart locks that won’t unlock to garage lights that randomly stop responding, we share real-world smart home frustrations. We also talk about Matter, Thread, hubs, and why the future of smart homes should mean fewer extra boxes and more reliable automations. 📞 When AI Customer Service Goes Wrong Damashe shares a frustrating experience with an AI phone system that slowed everything down instead of helping. We talk about what good AI customer service should look like and how companies are missing the point when bots just add extra steps. 🎬 Apple’s New Creator Subscription Apple now has a Creator bundle subscription that includes Final Cut, Logic, and more across Mac and iPad. We break down who it might make sense for and when it’s probably cheaper to just buy what you need. Support Technically Working by contributing to their tip jar: https://tips.pinecast.com/jar/technically-working Find out more at https://technically-working.pinecast.co Send us your feedback online: https://pinecast.com/feedback/technically-working/e1bbbb85-c1d5-48ad-bd90-4aa7d9cf011e Check out our podcast host, Pinecast. Start your own podcast for free with no credit card required. If you decide to upgrade, use coupon code r-431b7d for 40% off for 4 months, and support Technically Working.

View episode

Chunk the Text, Treat the Room, and Let Your Assistant Do the Follow-Up

Show notes (Technically Working, Episode 146) This week starts with a dramatic voice demo and turns into a practical conversation about TTS quality, accessibility, and the friction that slows down real work. In this episode, we talk about: More expressive on-device voices (and why “emotion” in TTS can be impressive but unpredictable) Why some AI voices drift over long reads (like losing low end after a few thousand characters) The practical fix: chunking text around 3,000 characters at sentence or paragraph boundaries The jarring side of expressive TTS: when the tone suddenly shifts mid-training Mac code editor accessibility and workflow: VS Code feeling clunky with VoiceOver navigation Nova being close, but still having VoiceOver quirks (like wrapped-line re-reading) Missing the flexibility and simplicity of TextMate A quick audio reality check: room reverb, mic position, and loud breathing in the mic Why it’s worth listening back sometimes, even if you usually don’t “Personal intelligence” assistants: Gemini connecting deeper with Gmail, Calendar, Photos, and Drive, and what that could enable Stream Deck Plus on sale (knobs!) and the bigger question: is the software accessible enough? Capture friction and follow-up problems: Getting ideas out of your head fast Using automation to sort notes into reminders, drafts, and follow-ups Why the Apple Watch action button might help reduce steps PLAUD recording devices: improved hardware button design, but app accessibility still matters Local processing ideas: Raspberry Pi options for local transcription and LLM workflows Listener feedback: Squarespace questions and a quick look at support options (tip jar vs Buy Me a Coffee) Feedback and contact: feedback@technicallyworking.show Support the show: Visit technicallyworking.show and click “Support Us” to leave a one-time tip or set up a recurring amount. Mastodon: @payown@dragonscave.space @damashe@technically.social @tw@technically.social Support Technically Working by contributing to their tip jar: https://tips.pinecast.com/jar/technically-working Find out more at https://technically-working.pinecast.co Send us your feedback online: https://pinecast.com/feedback/technically-working/1396d590-a7dc-4a88-8455-1b3da1991eb2 Check out our podcast host, Pinecast. Start your own podcast for free with no credit card required. If you decide to upgrade, use coupon code r-431b7d for 40% off for 4 months, and support Technically Working.

View episode

Teaching Tech, Tethering Pain, and a Little CES Talk

Episode 145: Teaching Tech, Tethering Pain, and a Little CES Talk This week we bounce between real life and real tech: why tethering still makes us want a MacBook with built-in cellular, what passkeys look like in the real world, and how Google Family Link pushes you into creating Gmail accounts for kids. We also talk honestly about teaching tech, why we often prefer working with people who are ready to level up their productivity, and how listener feedback shapes where the show goes next. Plus, a quick CES roundup with a few gadgets and ideas that actually stood out. In this episode Late-night work limits, and planning so tomorrow doesn’t get wrecked Tethering frustration, and the “just give us a MacBook with cellular” wish Michael’s living-room recording setup: Vocaster + OWC dock + Zoom, no virtual device chaos Google Workspace security alerts: suspicious login emails and what to check Passkeys: what’s great, what’s still confusing, and why some services still ask for a code Family Link and kids’ Google accounts: why Google requires @gmail.com, and how passkeys fit in Shared iCloud Passwords groups so parents can manage kids’ logins Password manager friction on Mac: Apple Passwords prompts vs 1Password workflows Listener feedback and the point of the show: it’s not a weekly “how-to,” it’s real conversations Teaching tech: beginner wins, real frustrations, and why “productivity level” training can be a better fit CES notes: mobility tech, batteries, smart locks, and a few other items that caught our attention Quick Surf app check-in: progress, but still clunky in places Support and contact info, plus Mastodon handles and the show hashtag Support Technically Working by contributing to their tip jar: https://tips.pinecast.com/jar/technically-working Find out more at https://technically-working.pinecast.co Send us your feedback online: https://pinecast.com/feedback/technically-working/c074c0cd-6feb-44da-bde8-e4a9321fd9f3 Check out our podcast host, Pinecast. Start your own podcast for free with no credit card required. If you decide to upgrade, use coupon code r-431b7d for 40% off for 4 months, and support Technically Working.

View episode

#144: Build and Create: Themes for 2026

New year, new themes. Michael and Damashe look back at 2025’s themes (education and infrastructure), then set 2026’s themes: build and create. They also dig into vending machine training realities, note-taking experiments with iPad, RSS reader options, subscription cleanup, and what to do when someone asks “Which AI should I use?”

View episode

#143: Testing Our Audio Stack and Rethinking Support for 2026

TW 143 Show Notes Testing Our Audio Stack and Rethinking Support for 2026 This episode is a wide-ranging, very on-brand Technically Working conversation that starts with audio workflow testing and ends with bigger-picture decisions about the future of the show. We spend time digging into what actually happens when we record with the Zoom Podtrack P4Next, , how computer audio is handled, and why VoiceOver and other system sounds can be harder to separate than people expect. A key takeaway is that once audio leaves your computer, it is just stereo audio, and whatever comes out is what gets recorded unless you do very intentional routing ahead of time. From there, we revisit the idea of switching from Cleanfeed back to Zoom. The main driver is flexibility. If one or both of us are away from a computer and need to record from an iPhone or iPad, Cleanfeed is not an option. Zoom gives us more freedom, removes a extra subscription, and opens the door to potential YouTube livestreams. We also talk about Zoom’s Original Sound setting and why it finally feels usable. Michael shares ongoing Raspberry Pi frustrations, including re-imaging systems, adding hardware based on advice from others, and why using separate microSD cards for different projects can be the right call. This turns into a broader conversation about hobby projects, learning by doing, and knowing when to ask for help. Damashe walks through discovering damage to his MacBook Pro screen in a very real-world way while trying to complete an ID verification process. That discovery leads to a plan involving AppleCare, backups, wiping machines, storage limitations, and the general annoyance of migrating between Macs with different capacities. We also talk about Bluetooth audio switching, why Apple’s automatic device switching is often more frustrating than helpful, and how shortcuts and third-party tools can give you back control over where your audio goes. Later in the episode, we read and respond to listener comments and reviews. We talk candidly about the structure of the show, why it does not follow a traditional format, and who it is actually for. We acknowledge critic Support Technically Working by contributing to their tip jar: https://tips.pinecast.com/jar/technically-working Find out more at https://technically-working.pinecast.co Send us your feedback online: https://pinecast.com/feedback/technically-working/439e0373-960e-4653-9a95-ff775003b7d7 Check out our podcast host, Pinecast. Start your own podcast for free with no credit card required. If you decide to upgrade, use coupon code r-431b7d for 40% off for 4 months, and support Technically Working.

View episode