Comments on: Time Crunch: Fewer Programmers = Faster Turn Around (and Better Results) https://davekz.com/more-programmers/ The Trials and Tribulations of a Programming Ninja Sat, 05 Oct 2013 15:29:40 +0000 hourly 1 https://wordpress.org/?v=6.5.5 By: Jacob Emerick https://davekz.com/more-programmers/#comment-392 Sat, 05 Oct 2013 15:29:40 +0000 http://www.david.kryzaniak.com/?p=636#comment-392 I think that most managers (non-technical managers) realize that it’s not purely additive yet they still think it helps. That 3 programmers can get a project done twice as fast, or maybe 5 programmers three times, as opposed to straight-up 3 programmers equals 3 times as fast. In my experience this gets frustrating because a) each hastily-added programmer is aware that they will not be outputting to their full potential (if they were working solo) and b) this is highly dependent on environment, background, and per-task management. Where this gets dangerous is when a project is behind and the manager is ‘willing’ to sacrifice the feelings of the programmers for a small potential increase in output.

You don’t blame the manager for poorly written code, you blame the programmer. The only person that should shoulder the blame or even be worried about approaching timelines is the manager. If a project is behind its the project manager’s fault for not laying out reasonable milestones, not appropriating resources at the correct times, or for not having the right people involved. More programmers will not help with poor project management.

Good topic, sir!

]]>