A developer argues that writing code by hand first, then using AI for maintenance, is more effective than AI generating initial drafts.
Explores whether CSS can be considered 'wrong', arguing that working code is valid and changeable.
Article discusses the true purpose of code review beyond bug-finding, emphasizing judgment, communication, and codebase health.
A quote from John Carmack on the pitfalls of over-architecting software for future needs.
Argues that AI coding agents can help developers produce higher quality code and reduce technical debt by automating tedious refactoring tasks.
Argues that AI coding agents should be used to improve code quality and reduce technical debt, not just speed up development.
Explains 5 essential architecture tests for .NET projects to enforce design rules and prevent technical debt using tools like ArchUnitNET.
Argues for rigorous scientific studies on the impact and risks of using LLMs in software development, highlighting current lack of impartial research.
A developer shares critical drawbacks of using Claude Code for AI-assisted programming, focusing on hidden issues like problematic test generation and maintenance challenges.
A critical analysis of why LLMs like Claude Code struggle with complex coding tasks, arguing the real issue is not intelligence but poor software engineering practices.
Explains the three key growth curves—exponential, linear, and logarithmic—that define a scalable software business and an engineer's role in building long-term assets.
A critical analysis of the '10x productivity' claims in AI-assisted software development, questioning quality and oversight.
Explores how software architecture principles for human cognition, like fractal design, could improve AI's ability to work with large codebases.
Explores how AI coding agents impact internal code quality, using a case study of adding GitLab support to a Swift app.
A developer shares key lessons from one month of AI-powered app development, focusing on the pitfalls of speed and the importance of maintaining control and code quality.
Martin Fowler's blog fragments discuss AI/works™ platform, AI electricity consumption, and the need for rigor in AI-enabled software development.
Argues that ugly, legacy code can hold valuable domain knowledge and be more practical to refactor than to rewrite from scratch.
A developer's reflection on the psychological impact and community effects of over-reliance on AI coding assistants, likening them to personal daemons.
Explores how AI prompts have evolved from simple text strings into critical, reusable system components with logic, and the challenges this creates.
A developer shares their Java solutions for Advent of Code 2025 puzzles, focusing on code clarity and using Java 25 features.
