
Eight Times More Code, Eight Times More Bugs?
With AI, we ship far more code. Should we accept far more bugs in return? No: quality isn't a function of how much you produce, it's a property of what you ship.
Read article →EPYCREST / BLOG
Analysis, field experience and methods for building software with artificial intelligence.

With AI, we ship far more code. Should we accept far more bugs in return? No: quality isn't a function of how much you produce, it's a property of what you ship.
Read article →
In a world where AI redefines our practices every week, what was innovative two months ago is already outdated. Our approaches, tools, and instincts must evolve at the same pace — and the people best equipped to help us stay on course aren't always who you'd expect.
Read article →
AI requires complete organizational transformation, not simple tool adoption. Organizations that succeed transform structure, processes, and culture to maximize sustainable ROI of 200-400%.
Read article →
AI generates locally consistent code but can create global architectural chaos. Paradox: it's also the most powerful tool for rapid refactoring. Organizations that exploit AI bidirectionally (generation AND remediation) maintain sustainable velocity.
Read article →
AI destroys the narrow specialization model by transforming the T-shaped developer from an aspirational concept to an operational necessity. The role shifts from execution to orchestration.
Read article →
AI generates 1.7x more bugs than humans, but these bugs are fundamentally different. This distinction changes the conversation about code quality and forces a transformation in development processes.
Read article →
AI promises spectacular productivity gains, but reality is more nuanced. Amplification exists and transforms the profession more than it accelerates it, requiring more judgment, rigor, and diverse skills.
Read article →