The most famous quote from Knuth’s paper “Structured Programming with go to Statements” is this: There is no doubt that the grail of efficiency leads to abuse. Programmers waste e…
In project management lore there is the tripple constraint: time, money, freatures. But there is another insidious dimension not talked about. That is risk.
The natural progession in a business if there is no push back is that management wants every feature under the sun, now, and for no money. So the project team does the only thing it can do, increase risk.
The memory leak thing is an example of risk. It is also an example of some combination of poor project management including insufficient push back against management insanity and bad business mangement in general which might be an even bigger problem.
My point, this is a common natural path of things but it does not have to always be tolerated.
deleted by creator
… and this is how IT ends up being responsible for a breach.
It is a bug, unexpected and undefined behavior - it shouldnt have been there.
You are not wrong about the outcome from a capitalist view, but otherwise you are.
Exactly.
If you are exiting with a memory leak, Linux is having to wipe the floor for you.
In project management lore there is the tripple constraint: time, money, freatures. But there is another insidious dimension not talked about. That is risk.
The natural progession in a business if there is no push back is that management wants every feature under the sun, now, and for no money. So the project team does the only thing it can do, increase risk.
The memory leak thing is an example of risk. It is also an example of some combination of poor project management including insufficient push back against management insanity and bad business mangement in general which might be an even bigger problem.
My point, this is a common natural path of things but it does not have to always be tolerated.