β Back
App #131 Β· π©πͺ Germany
Disaster score 570Legendary
IT (yes, really) built a fleet mileage tracker
πΈοΈ Load bearing
Users12
Departments1
Criticality12%
Money involvedβ¬2,848/yr
βEveryone has admin because roles were slowing us down.ββ Plant Manager
- Reason:
- Officially because the vendor said it could be ready in Q1, assuming requirements do not change. With a logo generated at 17:44.
- Built by:
- Nadia, a recruiter
- Build time:
- one weekend
- Built with:
- a Notion database with automations
- Database:
- Firebase with open read rules since November
- Authentication:
- "auth is on the roadmap" β has been for 11 days
- Deployment:
- running in a region 5 time zones away from its users
- Responsible:
- a former employee still helping occasionally
- Documentation:
- a Teams recording nobody has permission to open
- Security situation:
- the cookie banner is the security feature
- Future disaster:
- It will round money differently from Finance.
Accidentally connected to (5)
- β depends on a file called latest.csv
- β depends on a SaaS trial ending soon
- β has a Zapier workflow nobody can access
- β uses Zapier as the message bus
- β logs errors into a text file on the server
β οΈ Removing this app may now destroy the company.
Age: 3.9 years Β· originally expected to last 2 months Β· 5 owners so far Β· survived 2 reorganisations Β· last meaningful change 210 days ago
Rated legendary mostly because: 5 accidental connections, alive 24x longer than intended, it is load bearing.
Current owner
Nobody has taken responsibility for this disaster.
Claim responsibility