When I was in school I had a laundry app (forced to use) that took 8 seconds to load, mostly while it scanned the network for the machines. It also had the rooms out of order in the room listing and no caching so every time you wanted to check the status (assuming it even worked) it took no less than a minute. It usually took less time to physically check, which also had a 100% accuracy.

Fuck this "we don't need to optimize" bullshit. Fuck this "minimum viable product" bullshit. It's just a race to the bottom. No one paper cut is the cause of death, but all of them are when you have a thousand.

▲ andrekandre 2 days ago | parent [-]

  > No one paper cut is the cause of death, but all of them are when you have a thousand.

this is a common failure mode of projects unfortunately, and its precisely because paper-cuts have low signal-to-noise ratio that they are hardly worked on...

ironically, sometimes its the reactions to big issues that cause paper-cuts to flourish (aka red-tape, incident mitigation, rushing to deadlines, "temporary" bug fixes piling up etc etc)

	▲	godelski 2 days ago \| parent [-]
		I don't think it was papercuts. The company also had their API leaked and it made the news. 6 months later and it wasn't fixed and people were doing their laundry for free...