3 ms·
The person who told me about this was the person who counted up the code at the end of the project. And, yes, it was 250 from each, not 500 from each parent com
by ncmncm 5y ago
The person who told me about this was the person who counted up the code at the end of the project. And, yes, it was 250 from each, not 500 from each parent company. (Memory is funny that way.)
I do not doubt that the numbers were rounded for simplicity. It is meaningless to talk about a 499x engineer.
As was explained to me, this engineer assigned two-week work units. If the work was not ready at the end of two weeks, he wrote it himself over the weekend. So, a fair bit of code was written that did not make it into the final product.
- pseudalopex 5y ago> If the work was not ready at the end of two weeks, he wrote it himself over the weekend. Using no code or knowledge from the past 2 weeks?
- ncmncm 5y agoThat would have taken longer.
- pseudalopex 5y agoUsing it or not using it would have taken longer?
- ncmncm 5y agoTrying to use somebody else's code that does not solve the problem generally takes longer than writing it yourself.
- newaccount74 5y agoBut looking at someone elses code first generally makes you faster even if you end up not using any of it.
- pseudalopex 5y agoSolving a problem isn't all or nothing.
- druvisc 5y agoFor it to matter, it is.
- pseudalopex 5y agoNonsense. A house without electric outlets and switches isn't ready. It's much closer to ready than empty land.
- ahtihn 5y agoThat's a ridiculously wasteful way of managing work. I too can be a 10000000x engineer if I never let others actually merge their code and just write it myself instead.
- ncmncm 5y agoIt was a way that delivered product on deadline, for exactly that project. Every project has specific needs. If you code to some other project's needs, you do the wrong thing.
- Jensson 5y agoIf you hired engineers like they hired them before coding interviews combined with a decade of the dead sea effect I can easily see a team of 500 barely getting anything done at all. Big organizations are often grossly mismanaged like this which is why smaller organizations can beat them.
- deckard1 5y agomismanaged, yes. But also risk-adverse and encumbered with process. At a big corp you may need 5 or more sign offs on a single merge. I probably spend a good 40% of my time herding cats and babysitting the merge pipeline. There is a lot of overhead you simply won't find in a startup.