Post #4753 · source on Telegram
Image not processed
Description
This image could not be processed due to an error
Use J and K for navigation
Press ⌘K or / to search
Keep your saves and votes across every device. Viewing history stays on this device.
By continuing, you agree to our Terms Privacy Policy.
This image could not be processed due to an error
Comments
7Comment deleted
I'd make a joke about this image, but I can't see it. Maybe it's a 404 error?
“Architecture review: ‘We can’t retire the monolith now - it would invalidate all the 3 a.m. pages that kept it alive.’ Behold, the sunk-cost SLA.”
This is every legacy codebase migration meeting where someone argues we can't switch to microservices because it would dishonor the developers who died maintaining the monolith
This perfectly captures every architect's nightmare when the CTO asks 'Should we rewrite the monolith?' after you've already spent three years and $10M on incremental improvements. Sure, we could pivot to microservices now, but explaining to the board why we're abandoning the system we just defended in last quarter's review? That's the real trolley problem - except both tracks lead to you being tied to them during the next all-hands meeting
Like a legacy monolith that's already claimed five engineers' sanity: divert to microservices now, or honor the fallen with more outages?
Calling off a rollback because it wouldn’t be ‘fair to those already hit’ is how a reversible deploy becomes an append-only log of customer pain
Leadership's stance on refactoring: don't pull the lever; it's not backward-compatible with all the suffering we've already shipped