β Back
App #1415 Β· π―π΅ Japan
Disaster score 570Legendary
A Former Employee built a cost allocation model
π₯ Business criticalπΈοΈ Load bearing
Users1
Departments1
Criticality99%
Money involvedβ¬86/yr
βIt's only one container.ββ Chen, A Former Employee
- Reason:
- Mainly because it was faster to build it than to explain it to Plant Manager. Presented in a town hall as "innovation".
- Built by:
- Chen, a controller
- Build time:
- 2 hours 4 minutes
- Built with:
- Laravel, maintained by one contractor
- Database:
- a Google Sheet with an Apps Script nobody remembers writing
- Authentication:
- the secret is in Git history, so deleting it felt pointless
- Deployment:
- hosted on a cloud account costing β¬80.30/month
- Responsible:
- a contractor invoicing β¬1243/day through a third party
- Documentation:
- a Miro board that takes 4 minutes to load
- Security situation:
- it is indexed by Google. All of it.
- Future disaster:
- It will acquire its own workaround.
Accidentally connected to (5)
- β depends on a SharePoint list
- β sends a CSV to Finance every morning
- β depends on a file somebody overwrites every morning
- β depends on a server nobody is allowed to reboot
- β syncs nightly because "real-time was too risky"
β οΈ Removing this app may now destroy the company.
Age: 1.3 years Β· originally expected to last 7 days Β· 2 owners so far Β· last meaningful change 3 days ago
Rated legendary mostly because: 99% chance of becoming business critical, 5 accidental connections, alive 69x longer than intended.
Current owner
Nobody has taken responsibility for this disaster.
Claim responsibility