First, I appreciate this story, but it seems the author compares the build process of software to the production process of the car line. It's comparing the bu

First, I appreciate this story, but it seems the author compares the build process of software to the production process of the car line. It's comparing the build stage vs the literal produce-the-thing stage. I also think the stoppage of the production line happens in software. If my code breaks while in production, I grab as many log files and stats as I can, roll back the code, deploy, and then study exactly why everything failed, and if we recovered post rollback. That seems like the similar case on the car production line - haul the faulty model aside (get the logs/metrics), figure out exactly what happened, fix it. Who knows how the actual assembly line was put together. Maybe they iterated hundreds of times. I don't expect my code to fail in production, otherwise I wouldn't have put it in production, but I understand it _may_ fail. That's why I put in logging and metrics collection, the same way those engineers hauled aside the car.