News for hackers. Stuff that matters.
Re:Internal documents reveal the grueling way Tesla hit its ... by falcolas on Tuesday August 21, 2018 @04:47PM (#17813653)
> But who is going to give them money to shut down the production line again and retool everything to increase FPY?

I imagine that it's significantly cheaper to fix the problem (and identify a root cause) when the car is still in pieces than to disassemble the finished product to fix the problem.

As for re-tooling, that can be done down the line with a manual fix in place in the short term (after all, they're able to fix it manually after the assembly line is completed).

Much like how in software development it's cheaper and faster to fix a bug caught in development than it is in production.

Re:Internal documents reveal the grueling way Tesla hit its ... by Klathmon on Tuesday August 21, 2018 @06:29PM (#17814434)
Yes, but if you find a bug in development and you are days away from shipping, and you have a solution that fixes the problem but doesn't address the root cause, are you going to delay the whole launch so you can fix it before hand? or are you going to release with the patch, and fix the root cause later?

Now software is different than cars, but I'm gonna say that I'd go for the latter just about every time. Both as a developer, and as a user.