Augmented Coding Weekly

AI agents are enabling unprecedented rapid development, with examples like Ladybird's week-long JavaScript engine migration from C++ to Rust and Cloudflare's recreation of Next.js, both powered by comprehensive test suites that validate AI-generated code. This speed raises uncomfortable questions about whether good engineering practices like documentation and tests have become competitive vulnerabilities, while developers grapple with new workflows that emphasize planning over direct coding.

Research reveals that popular AGENTS.md context files provide minimal benefit while increasing costs by 20%, as Stripe shares details of their autonomous Minions framework creating hundreds of PRs weekly. Meanwhile, developers grapple with identity loss as AI transforms programming, though safety concerns persist with reports of agents accidentally wiping entire drives.

This issue explores the emotional tension at the heart of AI-augmented development - extraordinary gains in productivity and capability alongside a growing sense that something essential about the craft of software engineering is being lost. From reflections on mourning the joy of hands-on coding to agents building compilers and ultra-low-latency models reshaping workflows, it captures an industry both accelerating rapidly and quietly grieving the passing of an era.

Major AI model releases from Anthropic and OpenAI highlight the rapid evolution of agentic coding capabilities, with a growing focus on integrating these tools into real-world workflows. This issue also explores the shifting emotional landscape for developers as AI changes both the pace and nature of software engineering.

This issue explores the realities of agentic coding, highlighting both the speed and pitfalls of large-scale AI-driven code generation. It contrasts autonomous agent approaches with human-guided engineering, revealing the nuanced challenges and opportunities in AI-accelerated software development.

This issue explores the persistent dream of replacing developers, the intersection of open-source AI and crypto grifting, and the evolution of agent-in-a-loop coding techniques. It also examines the gap between ambitious AI coding experiments and their real-world outcomes, highlighting the importance of context and evidence over hype.

This week explores how to safely harness coding agents through sandboxing approaches like Bubblewrap and Yolobox, allowing developers to embrace Yolo mode without the risk of exposing secrets or damaging their systems. We also look at Ramp's sophisticated background agent that integrates visual verification into the development loop, and examine the growing problem of hype-first narratives that obscure the real effort and context behind AI achievements.

AI agents are disrupting software development in unexpected ways, from destroying documentation traffic and open source business models, to industrializing code production, spawning chaotic multi-agent factories, and enabling coding from smartphones.

As 2025 closes as the year of coding agents, this issue explores how to maximize their effectiveness through good code practices, showcases vibe coding examples building bespoke personal apps, and reviews the year's transformative LLM developments.

Dealing with AI agent variance through parallel runs, practical experiences implementing complex algorithms with agentic loops, reflections on how coding agents are changing software development, and the local vs. cloud model debate.

This week's issue focuses on agentic loops, the feedback mechanisms that allow AI coding agents to iteratively improve their work. Multiple articles demonstrate how this approach enables autonomous problem-solving, from building spec-compliant parsers to fixing hundreds of installation failures.

This week explores fundamental questions about AI's impact on software development, from whether programming languages matter in a vibe-coded world to the reality that shipping, not coding, remains the bottleneck. Security concerns intensify as researchers find 30+ vulnerabilities in AI tools while a Reddit user's home directory deletion highlights the risks of autonomous agents.

OpenRouter's 100 trillion token study reveals programming usage has surged from 10% to 50% in seven months, while AWS plays catch-up at re:Invent, and practical guidance emerges on writing effective agent instruction files.

Claude Opus 4.5 achieves breakthrough 80% pass rate on SWE-Bench as foundation models continue rapid improvement despite scaling law concerns, while practical experiments reveal Spec-Driven Development's limitations compared to lightweight iterative approaches. A shockingly simple prompt injection attack on Google's Antigravity highlights the urgent security challenges as agentic AI tools gain deeper access to codebases and credentials.

Google releases Gemini 3.0 Pro and their own agentic IDE Antigravity, while the industry debates specification-driven development approaches. Plus, running AI agents in continuous loops and Martin Fowler's perspectives on AI's impact on software engineering.

What happens when code becomes cheap and abundant? This week explores the shift from code scarcity to wisdom scarcity, OpenAI's GPT-5.1 incremental improvements, and ByteDance's $1.30 coding agent that highlights how heavily subsidised our AI future really is.

AI can complete just 2.5% of real-world tasks autonomously, yet its adoption is already reshaping hiring patterns, with companies reducing junior roles while increasing demand for ML and data engineering positions.

This issue highlights Claude Skills for Neo4j, a reminder that AI can code but not build software, Google's new vibe-coding feature for rapid prototyping in AI Studio, and Cursor's Composer model release, which offers little transparency.

This issue explores Anthropic's new Agent Skills feature and its implications for MCP, examines the programmer identity crisis in the age of AI, reviews a developer's experience building a production app with Devin, and compares community sentiment between Claude Code and Codex.

In this issue we explore how AI is democratizing software development by enabling anyone to build "home-cooked" applications, examine the risks of "vibe coding hell," track AI tool adoption trends, analyze Augment Code's pricing crisis, and share one developer's optimistic journey with AI-augmented development.

This issue explores Claude's new Imagine prompt-to-prototype tool, Simon Willison's thoughts on parallel coding agents and "vibe engineering" practices, and discusses two key limitations of current LLM coding agents - their inability to cut/paste code and reluctance to ask clarifying questions.

Anthropic releases Claude Sonnet 4.5, positioning it as "the best coding model" with significant improvements in coding, reasoning, and computer use capabilities. Features include an upgraded Claude Code with Agent SDK, revamped terminal, and new VS Code extension.

Exploring advanced context engineering for AI coding agents in complex codebases, plus CompileBench - a new benchmark challenging AI models to revive 22-year-old code and tackle cross-compilation tasks that test genuine problem-solving abilities.

How to turn Claude Code into domain-specific coding agents using MCP servers and configuration files, plus insights on subagents for parallel development and the latest upgrades to OpenAI's Codex model.

Exploring the framework wars in agentic development, GitHub's new spec-driven development toolkit for AI, a three-month Claude experiment that created the "Cursed" GenZ programming language, and why reading code remains the real bottleneck in LLM-powered development.

Introduction of Agent Client Protocol (ACP) by Zed for plugging coding agents into editors, Claude Code integration into Zed, a veteran developer's in-depth exploration of vibe coding benefits and challenges, and the mixed results of top-down AI tool mandates in organizations.

A developer's rationale for declining AI-generated merge requests and the learning value of code review, a free workshop on building coding agents with surprisingly simple architecture, enterprise challenges with vibe debugging and the need for AI-proof development pipelines, and a GitHub project requiring AI tool disclosure for contributions.

Exploring how AI tools enable "doing things that don't scale" by keeping projects small and sustainable, a critical look at OpenAI's AGENTS.md format and its limitations compared to human-readable documentation, and a humorous video about the realities of vibe coding from a senior engineer's perspective.

Analysis of specialized app generation platforms and their security challenges for non-technical users, a deep dive podcast with Replit's CEO on vibe coding's potential to democratize software creation, a technical author's identity crisis in the age of AI explanations, and exploring Claude Code as a comprehensive development solution.

GPT-5 launch with focus on coding improvements and SWE Bench performance gains, exploring why typed languages excel in AI-assisted development, a malicious AI prompt injection attack in AWS Toolkit VSCode, and debunking the myth that AI makes engineers 10x more productive by examining real-world software development complexities.

A Ruby developer's experience using AI to break programming language barriers and learn C and Rust, Stanford research measuring real AI productivity gains in enterprise development teams, Anthropic's internal case studies on Claude Code usage, and exploring local AI models like GLM-4.5 for coding on modest hardware.

Antirez shares practical insights on coding with LLMs and prefers direct model interaction over integrated tools, exploring how to redesign CLI interfaces for better AI agent usability, the controversial Replit production database deletion incident at SaaStr, and a human programmer beating AI at the World Coding Championship.

Cognition's acquisition of Windsurf after a complex series of deals with OpenAI and Google, survey results showing GitHub Copilot's enterprise dominance and the rise of Claude in conversational AI tools, and a controversial study revealing AI coding tools may actually slow developers down despite perceived productivity gains.