4 ms·
What? That's like saying that programming is easy because it's just typing. It's not about how fast the guy with the monitor writes things! It's about making t
by iopq 12y ago
What? That's like saying that programming is easy because it's just typing.
It's not about how fast the guy with the monitor writes things! It's about making the right choice when you're designing a system.
When I do programming by myself I go through many designs and refactorings.
If someone already mentioned "hey, don't allocate on the hot path" and "make a closure here instead of copy pasting" and so forth without me having to be concerned about code quality and performance I'd get things done faster. I usually implement a very naive first version. If after typing this up I already have 3-4 people fixing it, then my pull request can have good performance, style, etc. from the get-go and get merged pretty fast instead of constant "can you fix this, then I'll merge it?"
- lojack 12y agoI think we can all agree that the keyboard isn't the limiting factor here. Individual programmers at their own keyboards can all focus on separate problems. Two (or more) programmers with a single keyboard can only focus on a single problem at a time, but they get the experience and perspective of multiple developers. It's really just a matter of breadth of focus vs depth of focus. At a certain point adding more developers won't help and it will end up wasting resources. This may be as soon as you add a second developer, or maybe after you add 6 developers.