Why wouldn't a safety-critical software developer search obsessively for bugs that might harm his system ?

Question

(Won't a typical developer get a "bright idea" about recording data to media, perhaps using the media that also contains the operational program ? Won't there be a risk of incorrect source code for this "bright idea" being somehow accepted and used, corrupting the operational program ? Won't there be a risk of no-one bothering to continually check that all source code for "bright ideas" is correct and matches the object or executable code being used ")

Why would people who don't do this describe themselves as leaders ?

Answer 1

Because any obsession makes one ineffective?

Answer 2

There are two reasons. When you work for a company and develop something then it is owned by a company even if you personally designed it at home. It is a common line in a contract when hired that your ideas belong to the company. They will wait until they no longer have the job then develop it, and make millions off of it without sharing it with the company they work for.

Second, if they develop it for the company it will in turn make their job obsolete because they will no longer have something to do, the computer will be doing it for them. They could potentially run themselves out of a job by creating something that makes their job easier or functionable.

Also, if they let bugs happen then are in turn creating more work for themselves and creating a demand for their job therefor creating a way to make more money.

Answer 3

Once it works well, it is already obsolete.