loading...

How do you get new starters acquainted with your codebase?

github logo ・1 min read

Do you often have new starters join the team?

How do you help them get a project up and running on their machine for the first time?

I've met some teams that use a fully automated process (e.g one shell script), and others that use a mixture of automated steps and manual steps.

Happy Friday!

twitter logo DISCUSS (4)
markdown guide
 

This is probably a worst case scenario for most people. Our team was joined from two teams around a year ago, and immediately after that we were moved to another manager that did not work to form us into a cohesive team. We still have two groups of people with SOME knowledge about half of the applications, but nobody knows about them all. Add to this that all of our members are less than two years with the team and our data model is all hierarchical of undefined depth. The docs are an odd combination of non-existed and unorganized. This perfect storm means that when new people join they just have to grab a piece that needs attention and ask questions where they come across them. While our documentation and introduction process is abysmal, once you get into it you become a bit of a subject matter expert nearly immediately which brings a tremendous amount of identity.

 

'our documentation and introduction process is abysmal' 😂 Steady on don't make it too easy for the juniors!

 

I only joined the group last July! I'm suffering too!

Oh no you poor things. Probably a good time to suggest some improvements to your team?

Classic DEV Post from Mar 23 '19

Dude, get a debugger!

An introduction to basic problem solving by using a debugger (Beginners Level)

Evie profile image
Full stack developer and Hawaiian shirt lover from the UK. I love cheese, real ale and playing the drums :->