a thoughtful web.
Good ideas and conversation. No ads, no tracking.   Login or Take a Tour!
comment
kleinbl00  ·  1600 days ago  ·  link  ·    ·  parent  ·  post: Uber's 5.6 Seconds of Incompetence

    It's possible the self-driving dev teams were following a "move fast and break things" mantra, but I doubt it, we have more mundane explanations like company structure and pressure at all company layers to demonstrate progress.

A software team... had no safety department. They had literally no one responsible for safety. They hired a safety officer... seven months after they killed someone. That is chapter and verse a "move fast and break things" culture: they found their need for a subsystem of development after their lack of that subsystem caused a critical failure. A critical failure involving a fatality. You're prevaricating: you're arguing that this is somehow a "structure" problem when their "structure" was "software development and nothing else." Boeing's problem was they wanted things fast - that's what "no training requirements" means. And Facebook abandoned "move fast and break things" after they'd rolled Beacon out and gotten pilloried by everyone on the Internet and press. However, they doubled down on this approach to Libra which, contrary to your ignorance, is a sovereign currency controlled wholly by Facebook designed to be beyond the regulation or purvey of the host nations it is used within.

I get that you want this to not be about software developers' penchant for the callous disregard of human life, but what you're mostly doing is illustrating your naivete of the design process and software engineers' historical roles of completely disregarding consequences are very well embodied in the mantra "move fast and break things."

There was a time when you couldn't hurt people with software. Your very arguments are illustrating that you think that time is now. The evidence of the situation illustrates that it never has been. And this is why it's easy to hate software developers.