4 ms·
What the article doesn't mention is that the people making the money aren't the people writing the code (critical path or non). The people trying to make money
by Timwi 4y ago
What the article doesn't mention is that the people making the money aren't the people writing the code (critical path or non). The people trying to make money are usually responsible for workers feeling overworked, exploited and unappreciated. Sabotaging the critical path is an easy and obvious way to “take revenge” on the oppressor. Even when such intentional sabotage is not at play, the exploited workers probably just don't really care about the oppressor’s balance sheet.
The most effective way to mitigate this is to give workers appropriate time off, healthcare coverage, and a fair share of the profits. But no profit-seeking company will ever do that.
- Jiro 4y agoConsider the flip side of your suggestion: If you make money when the program works, that also means that you don't make money, or you make less money, when it doesn't. The last thing I need as a programmer is for a poor management decision to put me in a situation where a bug can be blamed on me and I can get my salary taken away. It's also a bizarre idea that your programs won't have so many bugs if your workers have healthcare. (I'm also skeptical that many programmers who are employed don't have healthcare in the first place.)