6/9/2023 0 Comments Rescue team evil genius glitchThe idea has obviously paid off hugely at least for some companies. That if you hire the smartest people, and remove all the obstacles you can,Īnd get rid of red tape, and just let them do what they feel they need toĭo, then you'll get better results than using normal methods with normal Many tech companies are based around the idea Many people groan when they hear this question, but I think we should giveĬredit where credit is due. So naturally I showed the Tesla plot to my new manager, who looked at it and asked the above question. They didn't scale any faster than they legitimately could scale. They didn't try to build a Model 3 on day 1, because they would have failed. Then they scaled up slowly, progressively fixing their scaling problems as they went toward slightly-less-luxury car models. When they had a small number of people, they built a car that was economical to produce in small volumes. Tesla is a neat example of working incrementally. I don't know for sure why that's the case, but it says something about improved automation, which they claim to have further improved for the Model 3 (not shown because I made this graph earlier in the year, and anyway, they probably haven't gotten the Model 3 assembly straightened out yet). Shipped suddenly went up rapidly compared to number of employees, and With the introduction of the Model X, units They roughly scaled employees at almost the same rate as they scaled Roadsters and nothing else) is when they released the Model X. Graph (other than how long they went while producing only a tiny number of Production (from entirely public sources, by the way beware that I might I wanted to see how otherĬompanies scale up, so I put together a little analysis of Tesla's Here's a trend from a randomly selected company. And now we're finally getting to the point of this presentation.īut before we introspect, let's extrospect! What went wrong in 2016? Well, I decided to find out. Or as my old manager would say, "Cadence trumps mechanism." They were a little longer in wall clock time, but maybe not CPU time. They crossed over the December holiday seasons when nobody did any work. Periodic slower releases, but when I looked into them, it turned out that Our average time between releases was about two months, probably due (If what I do best was actually solving the problem, I assumeīefore 2016 though, we had been doing really quite well. It was kind of a mess, so Iĭid what I do best, which is plotting it in a spreadsheet. We also had out-of-controlīug/task queues and no idea when we'd be done. Way back in 2016, we were having some trouble getting our team's releases out the door. Opinion, not necessarily the opinion of my or probably any other employer.] [Obligatory side note: everything I post to this site is my personal Particularly specific to just our company, so I've taken the slides,Īnnotated them heavily, and removed the proprietary bits. People seemed to enjoy it a lot more than I expected,Īnd it went a bit viral among co-workers. I did a talk at work about the various project management troubles I've seen The text below is much moreĭetailed though, if you want to actually implement the advice.] Recording and some slides that you might enjoy. Updated and shortened version of this talk at SREcon EMEA 2018. Series whose none of their games have PCGamingWiki pages, are generally not listed here for abbreviation purposes.An epic treatise on scheduling, bug tracking, and triageĭiscussion of this post is unusually useful. This is a manual list of games known to be available on Big Fish Games, a storefront that currently doesn't have its own individual store info slot on PCGamingWiki.
0 Comments
Leave a Reply. |