Is software development vulnerable to phonies ?

Are some areas of computing infested by phonies ?


If it’s not true, there’s no harm done, we can simply state it is not true.


"When you know a thing, to hold that you know it; and when you do not know a thing, to allow that you do not know it - this is knowledge." -- Confucius ...


But I noticed these loopholes:





3.


A person joins as a programmer when the system is of high standard.


One change is made to the system. A trouble report is generated.


Whatever the merits or demerits of the trouble report, the programmer chooses to


modify the system so that the phenomenon mentioned in the trouble report no longer occurs. This induces lots of other problems. New staff are recruited to handle the workload. Perhaps new staff recommend the original person be promoted because he is the most senior. In any event, the original person is promoted. The whole organisation is now in free fall.

Is software development vulnerable to phonies ?
This would appear to be the fault of the programmer in question, but many bugs can be the result of improper code in an existing code base. It could also be faulty or inaccurate documentation from previous development cycles or something as seemingly innocent as a patch to a compiler system that "breaks" old code done to previous standards. In any case, anything in freefall isn't necessarily dead, if it has time to open a parachute ;-)
Reply:No! Generally one seeks help when in difficulty. Calling for help isn't perculiar to programmers, but sharing knowledge helps a lot in practical software development.