Boeing delays 737 MAX software fix delivery
Man oh man. Having (loosely) followed this saga, it sounds horrifically similar to every other &quot;feature rush&quot; I&#x27;ve ever seen in software development. I know this a fiction, but I can just imagine the scene - boss comes into SWE meeting, says &quot;some other team implemented this thing that the higher-ups wanted, we have to change all of our stuff to make it work, and we only have X weeks&#x2F;months&quot; (common sin: deadlines before effort estimates). Then more issues are discovered in dev, SWE&#x27;s try to push back but are ignored (common sin: concerns are not heard). &quot;Scope is reduced&quot; (common sin: this ALWAYS happens with hard deadlines, but SHOULD NEVER happen with human safety involvement, although it still does all the time e.g. healthcare).<p>It&#x27;s not until some poor, senior engineer, who is probably one of their best staff, has a stellar reputation, and genuinely cares about their job, their team, the product, and the company ... they have to fall on the sword and TELL management what&#x27;s going happen: we&#x27;re not shipping this yet, IT IS NOT SAFE. Then that goes all the way up the chain, management at every level wrings their hands, &quot;how oh how did this happen?&quot; (although they specifically are talking about the missed deadline, not the safety concerns). It gets high enough that feeling is overcome by senior leadership wrath, which flows back down, and ultimately that engineer and their entire team is punished.<p>What a dumpster fire.