DEV Community

Cover image for Adding more devs to your project makes it slower

Adding more devs to your project makes it slower

Thomas Hansen on August 07, 2022

This is the first article in my myth busting series where the conclusion is not mine. In fact, the above sentence originates from the book called "...
Collapse
 
jmfayard profile image
Jean-Michel πŸ•΅πŸ»β€β™‚οΈ Fayard • Edited

Great article.

One dev can do in one month what two devs can do in two months

That's always possibly true, but it's especially true if you have multiple devs that are individually very good, very opinionated and who love to argue. And oh boy do developers love to argue!

At a previous job the front-end team was stuck for two or three weeks because there were passionate debates on how TypeScript imports should be ordered. PRs could not be merged before this was resolved because each one was reverting the imports in the "right" order. I'm not a front-end dev myself, so if someone knows why that's important, I would love to get to the bottom of this, even if it takes one month of hard work.

Collapse
 
polterguy profile image
Thomas Hansen • Edited

Hahahahaha :D

Some things are too important to be debated comes to mind ... ;)

Edit - Define "good". A big motivation for me with these articles is to redefine the meaning of the word "good developer". Today unfortunately, it's abused, and misunderstood, such that the dev that knows the most complex theory is perceived as "the best" - While often the exact opposite is true, as in the more pragmatic developer is better for all practical concerns. I once spent two hours quarrelling with a colleague over UTC best practices. Interestingly, we were mostly in agreement, something I tried to emphasise (in vain) to get out of the fight. However, he was persistent, and refused to stop shouting, until I showed him a Jon Skeet blog where my argument originated from.

Objective this guy was better than me. However, I created in 30 minutes what he failed to create in 4.5 months. Yet again, define "good" ... :/

Collapse
 
jmfayard profile image
Jean-Michel πŸ•΅πŸ»β€β™‚οΈ Fayard • Edited

Define "good". A big motivation for me with these articles is to redefine the meaning of the word "good developer".

That's a great question.

I would differentiate solo projects and working in a team.

For solo projects, do whatever makes you happy and productive.
Want to program in Haskell? Go for it.

When working in a team, I wish we had something like the Serenity Prayer

Lord, grant me the serenity
to accept the things that I don't love but are fine nonetheless;
courage to insist on things that really matter
and wisdom to know the difference.

Collapse
 
andrewbaisden profile image
Andrew Baisden

A nice article with so many valuable points.

Collapse
 
polterguy profile image
Thomas Hansen

Thx Andrew 😊

Collapse
 
wjk22 profile image
Wojtek Kalka

Nonsense, if you get good people development will be faster, usually people who code completely alone suck at coding because they never learned to work in a team well .. if you can't manage a team with 10 people you are just not a good team leader.

Collapse
 
polterguy profile image
Thomas Hansen

usually people who code completely alone

Linus Torvalds made git alone. Just sayin' ...

... but he probably "sux", right ...? ;)

Collapse
 
wjk22 profile image
Wojtek Kalka

if you compare 99% of the people with Linux Torvalds you make a huge logical mistake

Collapse
 
wjk22 profile image
Wojtek Kalka

A software development team should always be possible to comfortably feed on two pizzas

even bigger nonsense

Collapse
 
polterguy profile image
Thomas Hansen

Bring it up with Jeff Bezos, I'm sure he wants to hear your objections ... ;)

Collapse
 
wjk22 profile image
Wojtek Kalka

Just google many have objections to him a good team consists of 5-12 people, they will be very hungry with two pizzas