Refactoring without the rewrite: how to decompose complex code
How to tell refactoring, decomposition, and a rewrite apart, pin the behavior of legacy code, and change structure in steps you can roll back.
Stuzhuk Lab — Chemistry of Code
Chemistry of Code
← All posts
Tag
legacy
All blog posts with this tag.
Where Code Generation Ends and Engineering Begins
AI already writes working functions, but a product is architecture, context, risk, and accountability. The boundary between code and engineering, a 15-year legacy case study, and developer skills in 2026.
Can AI Understand a Codebase With 15 Years of History?
Millions of lines, hundreds of tables, dozens of integrations: what AI grasps in hours, where it fails, how teams deploy RAG and repo indexing, and why expert + model beats either alone.
How to Design a System That Will Last 10 Years
Why systems die from early architectural decisions, not outdated tech — and how to design for change, not features: module boundaries, domain modeling, data, ADRs, and a decade-long checklist.
The Most Expensive Mistake in ERP Architecture — Trying to Make the System Universal
Why the illusion of universality turns ERP into an EAV monster: lost performance, typing, and business meaning — and how to build around the domain, not abstract entities.
Why Most ERP Systems Turn Into Monolithic Monsters
The ERP success paradox: exceptions, technical debt, a single database, and the distributed monolith. Why the monster follows business growth and how to slow decay.