Thread by @GergelyOrosz

Two new joiners on a dev team.

#1: Spends most time understanding everything, questioning the status quo. Doesn't ship much (or at all). Team members roll their eyes.

#2: Ships a *lot* of good code from day one. The team is pumped, starts listening to their ideas quickly.

With #1, the new dev doesn’t build trust with the team. “I know better, trust me, without me having shown that I can contribute.”

With #2, the new dev builds up trust quickly (assuming they ship code the team needs). They’ll have more support from within to drive change.

I’ve seen talented devs fail to help a struggling team as they did not work alongside team members at all. And no matter the improvement ideas, no one listened.

Others turn teams around by keeping an open mind, joining the “grind”, then implementing those same improvements.

Lots of great responses 🙏 A few thoughts:
- My point was to build trust with the team first: driving changes is easier after.
- Yes, shipping code is not the only way to build trust.
- New joiners who complain a lot, but make no positive changes / don’t build trust don’t go far.