Flashback Friday: Comply and die

At this government-connected facility, all software development needs a final approval from upper management before it goes into production, says a pilot fish working there.

“The approval meetings involve a short presentation of the software, what has changed from the previous version and what bugs have been fixed,” says fish. “If upper management agrees, it’s approved and released and we go back to work on the next release.

“We only submitted bug reports for bona fide bugs that needed to be tracked for fixing, not for all code changes. If the change was an improvement, it went on our list of improvements for the future. If someone checked in a version with a missing comma, we just made the change to fix it.”

To read this article in full, please click here