AI Summary
5 min read"Understanding the fundamental flow of your application and the mechanisms and how everything works together, that is super important," Scott says, addressing a listener who admits 80-90% of their code is AI-generated and they can't do an HTTP request on their own anymore. This question—about skills atrophying—opens a potluck episode of Syntax that wrestles with five distinct but connected tensions: what happens to developer competence when AI does the typing, whether to switch editors, how to find flow state with agents, when to retire a working tool, and how to build polished UI outside the React ecosystem.
The Brain Drain Is Real—But Syntax Isn't the Core Problem
The listener's confession that they "couldn't even do an HTTP request with my own hands without AI" gets a serious answer. Wes and Scott agree the feeling of brain drain is not imaginary. "By not doing those things in repetition and by not allowing our brain to understand these processes, your brain is actually letting those neural pathways go away," Scott explains. He draws a crucial distinction between forgetting syntax (the arguments to a reduce callback) and losing understanding of how systems work end-to-end. Forgetting syntax is fine—Scott can't do the IE PNG fix from 20 years ago either. But if you stop caring how a request flows through your application, you'll hit performance issues and won't be abl
Continue reading the full summary in the app — free to try.
Read Full Summary →Free • No credit card required
Never miss an episode of Syntax - Tasty Web Development Treats
Get every new episode summarized in your inbox — free, ~5 minutes to read.
No spam. Unsubscribe anytime.
What you'll learn
- 1 (00:01) **Episode Introduction** - Wes and Scott kick off a potluck episode answering listener questions about AI, tooling, and skill atrophy.
- 2 (01:02) **Addressing AI-Induced Skill Atrophy** - A listener describes how 80-90% AI-generated code has made them forget basic tasks like making an HTTP request.
- 3 (06:05) **Is It Time to Leave VS Code?** - A listener questions if they should switch from VS Code to newer AI-focused editors like Cursor or Claude Code.
- 4 (13:21) **Hitting Flow State with AI Coding** - A listener asks how to achieve the deep, therapeutic flow state they used to get from manual coding when working with AI.
- 5 (19:17) **AT Protocol vs. Solid** - A listener asks how AT Protocol (from Bluesky) compares to Solid (from Tim Berners-Lee) for data ownership and publishing.
- 6 (25:00) **Which Single AI Subscription to Choose** - A listener asks for a recommendation on a single AI subscription if they can only afford one.
- 7 (33:56) **Knowing When to Drop a Working Tool** - A listener asks for advice on when to abandon a tool that still works but is becoming outdated.
+ Full timestamped outline available in the app
Show Notes
Scott and Wes answer your questions about coding in the AI era, atrophying skills from too much autocomplete, whether it’s finally time to leave VS Code, chasing flow state with agents, and which single AI subscription is worth your money. Plus: AT Protocol vs Solid, making your AI config portable across tools, and bringing Shadcn-level UX to server-rendered frameworks.
Show Notes
- 00:00 Welcome to Syntax!
- 00:57 AI-Generated Code: Are My Skills Atrophying?
- 06:03 Is It Time to Move On from VS Code?
- 13:19 Hitting Flow State with AI Coding
- 19:15 AT Protocol vs Solid: Decentralized Web Approaches
- 24:55 Which AI Should You Subscribe To?
- 30:23 Making Your AI Setup Portable Across Tools
- 33:56 When to Drop a Tool That Still Works
- 40:12 UX Quality for Traditional Server-Side Frameworks
- 44:14 Using Hermes and Self-Hosted AI Assistants
- 49:27 Sick Picks + Shameless Plugs
Sick Picks
- Scott: ESP32-S3
- Wes: Sharge ICEMAG3
Hit us up on Socials!
Syntax: X Instagram Tiktok LinkedIn Threads
Wes: X Instagram Tiktok LinkedIn Threads
More from this podcast