HS137: Did AI Turn “Everybody Codes” into “Nobody Codes”?
John Attil-Johnson and John Burke discuss how AI coding tools have fundamentally changed the "everybody codes" strategy, arguing that while AI can generate code quickly, logical thinking and code comprehension remain essential skills. They contend that the focus should shift from teaching everyone to code to ensuring everyone can read code and think logically to catch AI-generated errors.
Summary
The episode opens with listener follow-ups and friendly banter between the hosts about their long relationship before transitioning to the main topic. A detailed discussion about firewall definitions clarifies that while firewalls are theoretically configured as "deny all by default," in practice they often function differently, leading to broader discussion about zero trust models and defense-in-depth security strategies.
The main topic examines how AI coding has transformed the "everybody codes" movement that preceded it. John Burke notes that the push to get more people coding—particularly women—historically signals a field past its peak and about to be devalued, citing the example of Soviet doctors being predominantly female but low-status. The hosts discuss whether everyone should code given that AI can now generate functional code quickly.
John Attila-Johnson argues that coding's true value lies in teaching logical, detailed, precise thinking rather than syntax knowledge. He suggests that studying any discipline requiring logical precision—whether Pascal, Latin, or formal coding—provides benefits that AI cannot replace. Both hosts emphasize that AI is poor at consistency and logic, making human oversight critical.
The conversation explores technical debt, arguing that AI tends to incorporate poorly-written code into new programs because it lacks the logical discrimination to identify and exclude it. They discuss how the rapid improvement curve of AI tools makes revisiting code from weeks ago less attractive than recreating solutions fresh, potentially eliminating the debugging benefits of reusing mature code.
The hosts settle on a distinction between reading code and writing code: everyone should be able to read code with sufficient fluency to identify logical errors in AI output, but writing code fluently may no longer be necessary for most people. They acknowledge that computer science remains a vital field for fundamental research and mathematical discovery, but the pathway from coding bootcamps to lucrative careers has fundamentally changed.
About this episode
“Everybody codes” was an enterprise buzzword. In this era of AI vibe-coding and single-use coding, should everyone code? Should anyone code? John and Johna talk about enterprise strategies with respect to coding in the AI era, including what expertise to look for in employees. AdSpot Sponsor: Meter Meter delivers full-stack networking—wired, wireless, and cellular—to leading<a class="excerpt-read-more" href="https://packetpushers.net/podcasts/heavy-strategy/hs137-did-ai-turn-everybody-codes-into-nobody-codes/" title="ReadHS137: Did AI Turn “Everybody Codes” into “Nobody Codes”?">... Read more »</a><img height="1" src="https://feeds.packetpushers.net/link/22503/17370400.gif" width="1" />
Key Insights
- Burke observes that historical pushes to recruit women into fields often signal that field is past its peak and about to be devalued, citing Soviet doctors as an example where female-dominated professions had lower status and compensation.
- Attila-Johnson argues that coding's primary value is teaching logical thinking and precision rather than language syntax, suggesting Pascal or Latin could serve the same purpose and the skill matters more than the tool.
- The hosts contend that AI is fundamentally poor at logical consistency and reasoning, making human oversight essential regardless of how much AI improves, as logical flaws cannot be fixed by better models alone.
- Burke identifies a phase shift in code usage where rapid AI improvement makes recreating solutions from scratch faster than searching for or understanding existing code, changing incentives around code reuse and maintenance.
- The hosts argue that AI tends to incorporate poor-quality legacy code into new solutions because it lacks the logical discrimination to identify and exclude substandard implementations, thus amplifying technical debt.
- Attila-Johnson claims that the rapid rate of environmental change in software makes human comprehension of the deployment environment increasingly challenging, requiring machine tools like AI to navigate that complexity.
- Burke contends that flow diagrams generated by AI cannot be trusted to accurately reflect the actual code logic, as AI provides no guarantee the diagram aligns with the code it generates.
- Both hosts conclude that everyone should be able to read and understand code logic well enough to catch AI errors, but becoming proficient at writing code is no longer necessary for most people given AI capabilities.
Topics
Transcript
Hi, I'm John Attil-Johnson, CEO of Nemertes, here with my co-host. John Burke, CTO of Nemertes. And you're listening to Heavy Strategy, the show that tries to ask the right questions, not give the right answers. And before we dive into today's topic, we have a bunch of questions from listeners, so this is great. from listeners, so this is great. Before we dive into today's topic, just a quick word from our sponsor, Meter, which is the company building networks from the ground up. Meter delivers a complete networking stack, wired, wireless, and cellular in one integrated solution. With Meter, you get fast, secure, scalable connectivity without the burden of managing multiple providers or tools. Meter scales from branch…
Full transcript available for MurmurCast members
Sign Up to AccessMore from The Everything Feed - All Packet Pushers Pods
PP116: News Roundup—FortiBleed Reveals Password Cracking Is Alive and Kicking, Accenture Goes All-In on OT, and More
Jennifer Jabush and guest co-host Wolf Gerlich discuss major cybersecurity incidents including the SearchLeak Copilot vulnerability, the FortiBleed password-cracking infrastructure, North Korean NPM package compromises, and organizational acquisitions in the OT security space. They also cover concerns about age verification systems and a FIFA World Cup broadcast vulnerability involving weak client-side authentication.
IPB202: How to Get Hands-On IPv6 Deployment Experience
Ed Horley interviews John, an experienced network engineer, about practical ways to gain hands-on IPv6 experience at home. They discuss consumer-grade IPv6 setups, multi-homing challenges, ULA addressing, NAT/masquerading trade-offs, and how working with multiple historical protocols informs modern IPv6 design thinking.
N4N057: The Art of Troubleshooting
Ethan Banks and Holly Podbilak discuss a structured methodology for network troubleshooting on the NS for Networking podcast. They cover steps from gathering information and recreating problems to using tools like AI, logs, and packet captures, while emphasizing the human elements of staying calm, working as a team, and documenting root causes.
D2DO304: Observability in the Age of AI
Kyler Middleton and Ned Belovance interview Anuj Tyagi about AI observability, covering the unique challenges of monitoring AI stacks versus traditional applications, the importance of tracking token costs, implementing guardrails, and how tools like Agent Gateways and MCP servers add new layers of complexity to observability.
PP113: Patch Gaps, Pretexting, and AI Use for Crimes and Crimefighting: 2026 Verizon DBIR Highlights
Hosts Jennifer Jabush and Drew Connery-Murray discuss highlights from the 2026 Verizon Data Breach Investigations Report, covering shifts in attack vectors, ransomware trends, third-party risk, and AI's role in both cybercrime and enterprise security. The report is based on 31,000 incidents and over 22,000 confirmed breaches across 145 countries from November 2024 to October 2025. Key findings include vulnerability exploitation surpassing credential abuse as the top initial access vector, and 60% of breaches now involving third-party relationships.