Kickstart your transition from vibe coding to agentic engineering.
These resources will help you master the new paradigm of AI-assisted development, where agents become true collaborators that can handle entire codebases and ship production features. Each piece was chosen for its practical, real-world insights. I’ll keep this list updated as the field evolves.
How to Use Claude Code Effectively
Read the article by Philipp Spiess (@philippspiess) • June 2025 • 14 min
Philipp shares practical workflow tips for maximizing Claude Code’s effectiveness:
- Start fresh often: Use
/clearfrequently to prevent context drift and maintain focus - Precise prompts win: Provide extensive context, edge cases, and specific examples
- Iterate, don’t overwhelm: Break complex tasks into small steps rather than attempting large changes at once
- Advanced techniques: Use “ultrathink” for complex problems, interrupt early when things go wrong, and leverage Git worktrees for parallel work
- Safety first: Stage Git changes frequently and use them as checkpoints
Claude Code has fundamentally changed how I approach many programming tasks… The key is finding the right balance between automation and human oversight.
Agentic Coding: The Future of Software Development with Agents
Watch the video by Armin Ronacher (@mitsuhiko) • June 2025 • 37 min
Armin explores agentic coding as a transformative paradigm where AI agents become true collaborators rather than mere autocomplete tools, describing it as “catnip for programmers” that draws developers into addictive, energizing sessions. Claude Code emerges as the leading tool, with its terminal-based interface enabling powerful agent chaining and remote workflows that editor integrations can’t match.
- Context is king: Success requires rich context, descriptive function names, and simple codebases. Go, PHP, and basic Python work best
- Dev environment matters: Agents need centralized logging, clear error messages, and tools that fail loudly to recover from mistakes
- Terminal > Editor: Terminal interfaces enable agent nesting and composability that’s difficult in traditional IDEs
- Beyond coding: Agents excel at debugging CI pipelines, browser automation, file management, and even online sales automation
- Avoid context rot: Long-running tasks suffer from accumulated failures. Often better to restart than compress context
The early adopter programmers are just the beginning of a broader wave of agentic AI use.
I can’t sleep gud anymore - A Practical Guide to Agentic Computering
Watch the video by Mario Zechner (@badlogicgames) • June 2025 • 85 min
Mario shares his hard-won patterns for using Claude Code effectively on real projects, demonstrating workflows from ad-hoc scripting to complex cross-language porting live, revealing how to maintain control while leveraging AI’s speed. Also see his blog post “Prompts are code” for deeper insights into this paradigm.
- Claude changes everything but demands discipline: It writes terrible code but enables rapid iteration - the key is maintaining tight control and understanding what it generates
- Context is everything: Use CLAUDE.md files, structured documentation, and tools like
jqto query JSON databases instead of letting Claude waste tokens exploring your codebase - Survival tactics: Run with
--dangerously-skip-permissions, write task summaries before context compaction hits, and hack Claude Code via claude-trace to become better at context management - LLMs as a flexible ISA: Your prompts are code, your .md/.json files are state on disk - build deterministic workflows with human checkpoints for quality control
- Live demo on production code: Watch the prompts-as-code principle in action - porting changes across a large polyglot codebase (Java/C++/C#) using LSP databases and .json state files, turning 2-week tasks into 1-day sprints
It’s not about the AI being smart - it’s about being smart about the AI.
Claude Code Best Practices from Anthropic
Read the article by Anthropic Engineering • April 2025 • 15 min
Anthropic’s engineering team shares comprehensive best practices for maximizing Claude Code’s effectiveness:
- Customize your environment: Use
CLAUDE.mdfiles for context, curate allowed tools carefully, and install GitHub CLI for enhanced interactions - Adopt proven workflows: Follow the Explore→Plan→Code→Commit approach, leverage TDD, iterate visually with screenshots, and use “Safe YOLO mode” for autonomous tasks
- Optimize interactions: Be specific in instructions, reference exact files, course-correct early, and use
/clearto maintain focused context - Advanced techniques: Utilize multi-Claude workflows, git worktrees for parallel tasks, headless mode for automation, and subagents for complex problems
Claude performs best when it has a clear target to iterate against: a visual mock, a test case, or another kind of output.
Building a macOS App Entirely with Claude Code
Read the article by Indragie Karunaratne (@indragie) • July 2025 • 19 min
Indragie built and shipped Context, a macOS app for debugging MCP servers, with Claude Code writing ~19,000 of the 20,000 lines of code. Key insights:
- Context engineering matters: Detailed specifications and “priming” Claude with examples produces much higher quality code
- Modern Swift can be tricky: Claude is competent but sometimes struggles with recent language features
- Productivity transformation: Rapid prototyping, mock data generation, and automated release scripts made shipping a polished side project actually achievable
- The future is here: Massive productivity gains make the investment worthwhile
This represents a fundamental shift in how developers can work: AI agents aren’t just assistants but capable collaborators that can handle entire codebases.
It’s like I found an extra 5 hours every day, and all it cost me was $200 a month.
A Cautionary Perspective on AI Coding
Read the article by Alberto Fortin (@a7fort) • May 2025 • 8 min
Alberto offers a sobering counterpoint to AI coding enthusiasm after discovering fundamental structural issues in his AI-generated codebase. His key insights:
- AI limitations are real: LLMs generate inconsistent, poorly structured code and struggle to maintain coherence across multiple files
- Use AI as an assistant, not a lead developer: Best for specific tasks like renaming parameters, translating pseudo-code, or learning new languages
- “Vibe coding” is dangerous: Relying on AI without technical knowledge is “a recipe for disaster”
- Protect your skills: Over-reliance on AI risks degrading critical thinking and coding abilities
- Return to fundamentals: Sometimes pen and paper planning beats AI-generated solutions
I’m not asking it to write new things from scratch… I’m the senior dev. The LLM is the assistant.
The Evolution of Software: From 1.0 to 3.0
Watch the video by Andrej Karpathy (@karpathy) • June 2025 • 40 min
Andrej presents a framework for understanding software evolution through three paradigms: Software 1.0 (traditional code), Software 2.0 (neural networks), and Software 3.0 (LLMs programmable via natural language). LLMs are becoming the new operating systems where English is the programming language, fundamentally changing how we interact with computers.
- LLMs as infrastructure: Like utilities and semiconductor fabs, they’re centralized, capital-intensive services with high reliability requirements
- The “people spirits” paradox: LLMs have encyclopedic knowledge but jagged intelligence, hallucinations, and no persistent memory
- Partial autonomy is key: Apps like Cursor and Perplexity provide “autonomy sliders” letting users balance AI generation with human verification
- Natural language democratizes coding: “Vibe coding” makes software development accessible to anyone, but deployment complexity remains a barrier
- Agents need new interfaces: Documentation must evolve from human-centric (“click this”) to machine-actionable commands
We are at a historic moment where software is fundamentally changing… Being fluent in all three paradigms will be valuable for future engineers.