Hacker Newsnew | past | comments | ask | show | jobs | submitlogin

> This is mostly just laziness and apathy.

Sometimes it is attached to incentives, like monetary rewards (bonuses and promotions). I've seen someone promoted on the back of a "high-impact" project that was bug-riddled and constituted more than half the support calls for the rest of the team for at least a year, not to mention financial penalties for the organization. It wasn't laziness or apathy, just rational actors optimizing benefits from the current rules with inadequate oversight and/or penalties for adverse outcomes.



If you can prove that a given KPI can be mapped to the bottom line, then you really have something. Usually it isn't this simple.

Was the high impact project rushed or was it staffed with crappy devs? Or both? Usually that is the reason for bad outcomes.




Consider applying for YC's Summer 2026 batch! Applications are open till May 4

Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: