markdown guide
 

You start with what is lacking, this way you will get to know the system and fix its mistakes:

  • documentation - if is missing start writing one
  • tests - if they miss start writing those

To do these you have to talk to other team members that are familiar with it and its clients, and of course read its code. After these you will have the "courage" to change the code.

 

May be useful to start exploring failure cases in a controlled environment too, if that's possible. Adrian's suggestions are great first steps towards preventing turnover from becoming a problem in the future.

 
 

Jump right in! Start fixing bugs and learn how the ins and outs are working.

It’s be like starting a new job. And knowing this was a failing point in the past, don’t let it be a failing point in the future. Ie: more then one person should know what’s going on and there should be some documentation.

Classic DEV Post from Mar 6

7 Tips for Breaking Into DevRel

How to get into developer advocacy & relations.

Ben profile image
A developer in Hong Kong. Learning And Rethinking as a developer. Welcome to contact me and make friend with me. Cooperation is welcome.

A blogging community of over 100,000 software developers Join dev.to