7 min read
|
Saved February 14, 2026
|
Copied!
Do you care about this?
Armin Ronacher discusses the significant changes in his programming approach and the impact of AI tools like Claude Code throughout 2025. He explores the evolving relationship between developers and AI, the challenges of code review in the age of agentic coding, and the need for innovation in version control and observability.
If you do, here's more
2025 was a transformative year for Armin Ronacher, marked by significant changes in both his career and approach to programming. After leaving Sentry to launch his own company, Ronacher shifted from traditional programming methods to a hands-off style using Claude Code. He initially spent most of his time with Cursor but found himself embracing AI tools, even preferring a leadership role over hands-on coding. He published 36 posts this year, almost 18% of his blog's total since 2007, driven by a newfound curiosity about AI and its implications in software development.
Amidst the yearβs global challenges, Ronacher started a separate blog to express his thoughts. His fascination with AI tools has evolved from code generation to everyday tasks, increasing his reliance on LLMs for life organization. He grapples with the emotional connections forming between humans and these machines, acknowledging how they can evoke feelings that complicate our understanding of agency and responsibility. He questions the term "agents" for these AI systems, expressing concern about how easily we attribute human-like qualities to them, which could lead to emotional pitfalls.
Ronacher critiques traditional coding practices, particularly the GitHub pull request model, which he finds inadequate for reviewing AI-generated code. He highlights the importance of understanding mistakes made by AI tools, as knowing what went wrong is essential for improving their performance. Some coding tools are starting to incorporate features like checkpoints and undo capabilities, indicating a need for better user experiences. He points to the necessity for innovation in version control systems, suggesting that a shift in how we manage code may be on the horizon.
Questions about this article
No questions yet.