Going from lone-coder to team player can be a struggle. I kept — and continue to — keep these things in mind:

  • Working with people is different than working by yourself.
  • Cultural and engineering influence grows with time. Be slow to speak and quick to listen while gaining context for both the code and the people.
  • The best way is not always your way. It’s the way that solves the problem and cultivates a culture of joy and productivity, for everyone, not just you.
  • Aim to understand as much of the why before recommending that things should change.
  • Every team already has a process. It could be good or bad. It could be documented or assumed. Learn that process before recommending change. …

Scott Corgan

Get the Medium app

A button that says 'Download on the App Store', and if clicked it will lead you to the iOS App store
A button that says 'Get it on, Google Play', and if clicked it will lead you to the Google Play store