"Welcome to 'Technically Working', the go-to podcast for tech enthusiasts and productivity seekers alike. Hosts Michael Babcock and Damashe Thomas take you on a journey through the ever-evolving world of technology and productivity. As Mac OS and iPhone users, they share their personal experiences and tips on staying productive while using these tools. But they don't stop there - they also explore other platforms like Android and Windows to bring you a comprehensive view of the tech landscape. Tune in each episode to hear them keep each other accountable, discuss the latest tools and strategies, and share their journey to reaching their goals. Whether you're a small business owner, freelancer, or simply looking to boost your productivity, 'Technically Working' is the perfect podcast for anyone looking to level up their tech skills and get things done."
Technically Working
Claim This Podcastby Damashe Thomas and Michael Babcock
Podcast Authority
Beta
Podcast Overview
"Welcome to 'Technically Working', the go-to podcast for tech enthusiasts and productivity seekers alike. Hosts Michael Babcock and Damashe Thomas take you on a journey through the ever-evolving world of technology and productivity. As Mac OS and iPhone users, they share their personal experiences and tips on staying productive while using these tools. But they don't stop there - they also explore other platforms like Android and Windows to bring you a comprehensive view of the tech landscape. Tune in each episode to hear them keep each other accountable, discuss the latest tools and strategies, and share their journey to reaching their goals. Whether you're a small business owner, freelancer, or simply looking to boost your productivity, 'Technically Working' is the perfect podcast for anyone looking to level up their tech skills and get things done."
Language
🇺🇲
Publishing Since
1/28/2023
Unlock The Full Podcast Authority Score Report
See how your podcast performs across key metrics
Podcast Authority
BetaRecommendations available
Unlock the full report to see detailed tips
Recommendations available
Unlock the full report to see detailed tips
Unlock comprehensive insights including:
- • YouTube presence analysis
- • Social media reach metrics
- • RSS compliance scoring
- • Podcast 2.0 features
- • Technical standards
Detailed Analytics
- Complete breakdown of all 19 authority metrics
- Personalized recommendations for each metric
- Industry benchmarks and comparisons
- Technical RSS feed analysis and compliance scoring
Growth Strategies
- Step-by-step action plans for improvement
- Quick wins to boost your score immediately
- Pro tips from successful podcasters
See how your show performs across every key metric
High authority scores make your podcast more attractive to industry leaders and influencers who want to appear on credible shows.
Sponsors look for podcasts with proven authority and engagement. Your score demonstrates your podcast's value to potential partners.
Understanding your strengths and weaknesses helps you make data-driven decisions to expand your listener base effectively.
1 verified contact email on file for Technically Working
Pitch yourself as a guest, propose sponsorships, or reach out directly to the host.
Recent Episodes
June 7, 2026
#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.
June 1, 2026
#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>
May 25, 2026
#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>
177 total episodes available
Similar Podcasts
Discover related shows you might enjoy
Double Tap
Double Tap Productions Inc.
Access On
National Federation of the Blind
Tek Talk
Accessible World
At Your Fingertips - Braille Then and Now
Chris Cooke
Mystic Access Podcast
Chris Nova, Kim Nova
Audio Pizza
Garth Humphreys
RNIB Tech Talk
RNIB Connect Radio
In Touch
BBC Radio 4
Mac Geek Gab — Your Questions Answered, Tips Shared, Troubleshooting Assistance
Dave Hamilton, Pilot Pete & Adam Christianson
MacBreak Weekly (Audio)
TWiT
Clockwise
Relay
Connected
Relay
Accidental Tech Podcast
Marco Arment, Casey Liss, John Siracusa
This American Life
This American Life
Deep-dive analytics for Technically Working
Frequently asked questions
Have a different question and can't find the answer you're looking for? Reach out to our support team by sending us an email and we'll get back to you as soon as we can.
- What is Technically Working?
- How often does this podcast release new episodes?
This podcast updates daily.
- Where can I listen to this podcast?
This podcast is available on 9 platforms including Apple Podcasts, Spotify, and more. You can also use the RSS feed directly.
- Does this podcast accept guests?
Information about guest appearances is not available.
Legal Disclaimer
Pod Engine is not affiliated with, endorsed by, or officially connected with any of the podcasts displayed on this platform. We operate independently as a podcast discovery and analytics service.
All podcast artwork, thumbnails, and content displayed on this page are the property of their respective owners and are protected by applicable copyright laws. This includes, but is not limited to, podcast cover art, episode artwork, show descriptions, episode titles, transcripts, audio snippets, and any other content originating from the podcast creators or their licensors.
We display this content under fair use principles and/or implied license for the purpose of podcast discovery, information, and commentary. We make no claim of ownership over any podcast content, artwork, or related materials shown on this platform. All trademarks, service marks, and trade names are the property of their respective owners.
While we strive to ensure all content usage is properly authorized, if you are a rights holder and believe your content is being used inappropriately or without proper authorization, please contact us immediately at hey@podengine.ai for prompt review and appropriate action, which may include content removal or proper attribution.
By accessing and using this platform, you acknowledge and agree to respect all applicable copyright laws and intellectual property rights of content owners. Any unauthorized reproduction, distribution, or commercial use of the content displayed on this platform is strictly prohibited.