How Misjudging the Importance of an Unloved Project can Turn Into a Dis
summary
A legacy hosting product serving 1,000 clients and delivering only 5% of revenue runs on a 12‑year old seph 50 TB cluster, goes offline after a power failure, and spends four days failing to resync storage, seven days restoring S3 backups and two weeks of five engineers to revive core services; 15–20% of customers leave, a €20,000 external fix is considered, and the business moves core services to AWS managed offerings while tightening QA and Well‑Architected checks.
AI-written summary · about
chapters (6)
- 0:00Introduction and project background
- 3:16Why legacy projects become disasters
- 8:04The power failure and recovery chaos
- 12:12Business impact and emotional attachment
- 16:53Root causes and hard lessons learned
- 17:37Summary and next steps
related talks
18mMaking what you have enough
28mThe Failing CTO - What we can learn from others' mistakes
20mDoing Things the Hard Way
30mLearning from Learnings: Anatomy of Three Incidents
11mA Failed Project and the Technical Architecture That Saved It
43mIf security is hard, you are doing it wrong
41mThe monolith must die! - How to convince managers
50mDevOps Project Failures - Lessons Learned and Strategies for Recovery