ipi

Recently accepted an offer to join a small size company as a mid developer. From the internal scoop and the interview I already know the code base is not great. There is a lot of technical debt, legacy tooling, poor coding practices and a lot of junk. I don't want to give up and just write more cruft or throw tantrums and pester everyone to re-write stuff.

If you are in my position, How would you approach ? What are the methodologies you follow to get yourself comfortable to start contributing to the existing codebase ? How do you gain existing team's confidence so as to persuade them to make some changes instead of sounding bossy ?

I faced similar situation in previous position and find it really difficult to get started. Any pointers are welcome!

"Stop thinking about creating the perfect end product and create a framework under which the right systems can emerge and continue to grow as we learn more."

Not sure where I read this but found it while reading about software architecture. It kinda stuck with me. Any other resources which helps gain more understanding on this approach and implementing it. Any products out there which does this better.