<story><title>How the Boeing 737 Max disaster looks to a software Developer</title><url>https://spectrum.ieee.org/aerospace/aviation/how-the-boeing-737-max-disaster-looks-to-a-software-developer</url></story><parent_chain><item><author>rkagerer</author><text>&lt;p&gt;&lt;pre&gt;&lt;code&gt;  I believe the relative ease — not to mention the lack of
  tangible cost — of software updates has created a cultural
  laziness within the software engineering community.
&lt;/code&gt;&lt;/pre&gt;
-- This --^&lt;p&gt;As someone who carefully crafts their code to strive for perfection, seeing sloppy work out there in the wild drives me nuts.  I know folks here will deride me for being &amp;quot;inefficient&amp;quot;, but in the long term I still maintain from my experience it&amp;#x27;s less efficient to push out buggy software and try to fix it retrospectively.</text></item></parent_chain><comment><author>anbop</author><text>Well, great code is inefficient if the impact of bad code is minimal. If you are shipping an animated emoji you should be sloppier with your code than if you are building flight control software. Overengineering software is like over-specing building materials by 10x and spending way more money on a building than it needs.</text></comment>
<story><title>How the Boeing 737 Max disaster looks to a software Developer</title><url>https://spectrum.ieee.org/aerospace/aviation/how-the-boeing-737-max-disaster-looks-to-a-software-developer</url></story><parent_chain><item><author>rkagerer</author><text>&lt;p&gt;&lt;pre&gt;&lt;code&gt;  I believe the relative ease — not to mention the lack of
  tangible cost — of software updates has created a cultural
  laziness within the software engineering community.
&lt;/code&gt;&lt;/pre&gt;
-- This --^&lt;p&gt;As someone who carefully crafts their code to strive for perfection, seeing sloppy work out there in the wild drives me nuts.  I know folks here will deride me for being &amp;quot;inefficient&amp;quot;, but in the long term I still maintain from my experience it&amp;#x27;s less efficient to push out buggy software and try to fix it retrospectively.</text></item></parent_chain><comment><author>adreamingsoul</author><text>Recently, I had someone join my team who was instantly popular and everyone enjoyed this person&amp;#x27;s personality. I trusted this person more then I should have and during a period when I was unable to give enough attention to their code reviews, they introduced several critical bugs and defects into the production environment.&lt;p&gt;I never figured out if it was ignorance or laziness. But, either way I learned a valuable lesson. It was also a reminder to me that not everyone has the same level of ownership or commitment that I would expect.</text></comment>