4 ms·

They are not struggling. This Yahoo article is fear mongering. I just listened to the whole earnings call and everything sounded terrific: They pulled their bes

They are not struggling. This Yahoo article is fear mongering. I just listened to the whole earnings call and everything sounded terrific: They pulled their best engineers to Gigafactory to mitigate a supplier misleading them about one of their battery production lines, and so they dropped production of S and X. Apparently as a result of the supplier f* up, they rewrote "20 man years of software in 4 weeks". Which is absolutely incredible. Don't listen to this fear mongering BS. Tesla is the only one in the electric car game. Who else has the charging network, the half-million pre-orders, the 3.5 billion in cash and easy ability to raise more, the Elon shine? Can't stand these articles

richardknop 9y ago
Rewriting "20 man years of software in 4 weeks" cannot result in anything else than bug ridden convoluted spaghetti code in my opinion. That is nothing to brag about.
FireBeyond 9y ago
> they rewrote "20 man years of software in 4 weeks". Which is absolutely incredible ... if accurate, if bug-free (for varying reasonable values of same). Otherwise the mythical man-month seems to creep in. That's a project that's complicated enough to require 240 developers (12 months x 20 years, fitted into 1 month), yet somehow was reliably chunked up, retrofitted into their supplier screw up, tested and deployed in 4 weeks?? I'm considering myself skeptical.
- StephenMelon 9y ago
  Sounds a bit like doing the Kessel Run in 12 parsecs? Seriously though, you can probably redo a typical 20 Man Year project in 2, given how much of the development process is usually taken up by missed requirements and re-work, IF you have a bombproof specification and a well-drilled team of stars. The part I’m not quite getting though is how a battery software issue impacted on wider productivity? Couldn’t they get them in-place and then patch the software after the fact?
draw_down 9y ago
Hmm, sounds to me like they are not doing so well. I wish them luck.

richardknop 9y ago

Rewriting "20 man years of software in 4 weeks" cannot result in anything else than bug ridden convoluted spaghetti code in my opinion. That is nothing to brag about.

FireBeyond 9y ago

> they rewrote "20 man years of software in 4 weeks". Which is absolutely incredible ... if accurate, if bug-free (for varying reasonable values of same). Otherwise the mythical man-month seems to creep in. That's a project that's complicated enough to require 240 developers (12 months x 20 years, fitted into 1 month), yet somehow was reliably chunked up, retrofitted into their supplier screw up, tested and deployed in 4 weeks?? I'm considering myself skeptical.

StephenMelon 9y ago
Sounds a bit like doing the Kessel Run in 12 parsecs? Seriously though, you can probably redo a typical 20 Man Year project in 2, given how much of the development process is usually taken up by missed requirements and re-work, IF you have a bombproof specification and a well-drilled team of stars. The part I’m not quite getting though is how a battery software issue impacted on wider productivity? Couldn’t they get them in-place and then patch the software after the fact?

draw_down 9y ago

Hmm, sounds to me like they are not doing so well. I wish them luck.