What are the biggest challenges when onboarding and contributing to a new codebase/project?

Jonathan Carter - Sep 14 '19 - - Dev Community

Hey All!

In your experience, what have been some of the biggest challenges you (or others on your team) have faced when getting setup and familiar with a new codebase, and then ultimately, merging in your first change? For example:

  • Setting up your machine with the right SDKs to build/run the app (e.g. specific version of Node/Java)?

  • Knowing which IDE and extensions are needed in order to productively work on the app?

  • Configuring access to private repositories, package managers or registries?

  • Setting up the needed service dependencies for the app (e.g. a database)?

  • Actually getting familiar with the codebase itself? (e.g. it’s directory organization, any specific style conventions)

  • Understanding architectural decisions that have been made, and how to best apply those for future work?

  • Learning the team processes for how to handle commits/PRs (e.g. thoughts on rebasing, do we use conventional commits?)

  • Determining who to ask questions about specific parts of the codebase?

  • Something else?

Many of these have potential solutions, and so I’d love to hear not only what challenges you’ve faced, but also, how you’ve worked around them. In general,
I’m just very curious to hear how teams are able to improve the onboarding and contribution process for new members. Thanks!

. . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Terabox Video Player