Design and Architecture: Special Dumpster Fire Unit
summary
A rewrite aimed to replace a system built for seven customers escalates into three successive versions that take 8 years instead of 3, add 18 planned customers but deliver late, and cost eight figures. The team abandons j2ee to Spring without experience, designs a metadata‑driven “fits anything” model, refuses no MVP incremental releases, repeats past assumptions from one customer, and delivers partial, operationally poor systems rather than a working product.
AI-written summary · about
chapters (4)
related talks
27m“Good Enough” Architecture Part 2
31m“Good Enough” Architecture Part 1
59mArchitecture Modernization Anti-Patterns: The Cost of Good Intentions
33mFrom Enterprise Architecture to Software Design - Critical Thinking
57mSoftware Architecture: The Hard Parts
29mFrom big to small and back again
48mIT Architecture : All your micro-services are wrong PERIOD!
44mDemonolith the Monolith Think Again!