I do not appreciate when authors use the royal "we" to speak for all software engineers when admitting to low quality-control standards.
I suspect that it is an attempt to broach an uncomfortable topic through vulnerable self-disclosure, but we need to be serious about admitting when there is a problem somewhere.
"Bugs" are not any more cute or fuzzy or entertaining or harmless than the engine "gremlins" that haunted the aviation industry back in the day.
I don't know how many accidents had to happen before the airplane people got serious, but software people are overdue for a similar reckoning.
"We all could have done more.": said by every politician. Which is easier: writing good code, or winning a political battle over crappy code? I mean, if you're not capable of coding, and creating an appropriate architecture for the the domain: which course of action gives you the most control over risk management? So yeah most fights about software are about politics and crappy code.
Saying this to set expectations based on having a business license since 1984.
xtajv · · focus · HN ↗
I suspect that it is an attempt to broach an uncomfortable topic through vulnerable self-disclosure, but we need to be serious about admitting when there is a problem somewhere.
"Bugs" are not any more cute or fuzzy or entertaining or harmless than the engine "gremlins" that haunted the aviation industry back in the day.
I don't know how many accidents had to happen before the airplane people got serious, but software people are overdue for a similar reckoning.
m3047 · · focus · HN ↗
Saying this to set expectations based on having a business license since 1984.