I am just saying that many successful biotechs were built on shoddy Unix scripts.

We don’t have to go that far anymore, but if your programmers are swearing at you in five years about your terrible code, that’s a win! You lasted five years and grew enough to hire judgmental programmers! Congratulations!

- Michele busby

My brother works in fintech sector. He had created an Options strategy after months of hard work and deployed the strategy in production via CI/CD.
However, the strategy didn't deploy automatically on Monday and few trades didn't happen leading to loss. His boss came down firing at him as to why strategy was not deployed.

Turns out the IT team had changed the password on Friday evening as per their routine password updates.

The reason why developers should know the whole context of problem statement rather than just demanding requirements
Or
why the managers should set up the context of the problem rather than expecting magical solutions

We are soldiers, we don't ask questions - we take orders!

Normal person : 365 + 1 = 366
Developer dealing with julian dates : 365 + 1 = 1(New year)
Business person : 365 + 1 = 001 (because they like symmetry in their file names with dates)

We found this BUG, now we are celebrating our new year by changing code in each of script to format string accordingly.

Why "hungry" developers can't succeed in life?
Here is the reason!