3 ms·
I think that there are more weak points where sports analogy breaks - sports is generally about preparing for competition and competition is not a daily event.
by Ingon 10y ago
I think that there are more weak points where sports analogy breaks - sports is generally about preparing for competition and competition is not a daily event.
If we continue with this analogy this would mean that the developers should be training for a while before hitting a day (or week) of an actual work, but we are actually expected to treat every day as a competition day. Another point is, that the training varies over the period with every practice having a different goal - some are harder, some are easier and there is a great emphasis on rest and not over-training. And finally, sports are frequently cyclic, based around seasons - with competition and non-competition seasons. Competition seasons are about getting to a top performance so you can hit these N competition with all you can, while non-competition ones are all about resting and getting your sanity back.
So, while there are some parallels, I don't think this is a great analogy. I don't think getting top performance day after day is possible on regular basis, but, unfortunately, some people are certainly expecting it.
- CydeWeys 10y ago> I think that there are more weak points where sports analogy breaks - sports is generally about preparing for competition and competition is not a daily event. It truly depends on the sport. On one extreme you have sports like marathon or Olympic lifting, which require elaborate cycles of months of training designed to deliver peak performance on an exact date. But then on the other extreme you have sports like baseball, for which the season is half the year long and has players playing games almost every day. So there competition is a daily event, and the analogy to programming is more apt.