←back to thread

268 points behnamoh | 1 comments | | HN request time: 0.239s | source
Show context
capableweb ◴[] No.28668272[source]
This is good advice but forgets that people are part of how long time something will take as well. If it's one engineer, it'll probably take $estimation * π, but if it's two engineers, you probably need to double that. If it's three, triple it. New calculation should be something like "($estimation * π) * $peopleWorkingOnSameThing". Communication overhead and mistakes should not be underestimated.
replies(4): >>28668376 #>>28668394 #>>28668452 #>>28688773 #
Aeolun ◴[] No.28668394[source]
Wait, so you are saying that the net positive effect of adding an extra engineer is zero?
replies(3): >>28668455 #>>28668719 #>>28669416 #
1. hemric ◴[] No.28669416[source]
In my experience it may most of the time take longer time to have stuff done BUT what is implemented will be better engineered and robuster. As long as you do some pair-programming and pair code review from time to time, the fact that you must develop a system that is understandable by more people leads to a better architecture.