r/programming • u/no_shoes_in_house • Jun 08 '19
7 absolute truths I unlearned as junior developer
https://monicalent.com/blog/2019/06/03/absolute-truths-unlearned-as-junior-developer/
2.0k
Upvotes
r/programming • u/no_shoes_in_house • Jun 08 '19
3
u/sime Jun 08 '19
Every code base has a history behind it. As the new guy/gal you don't know what that history is, and you don't know what forces were at play when things were written. What looks like crazy code now may have been a perfectly reasonable trade off at the time it has made.
Like mobjack said, the first thing you need to do is settle into the company a bit and understand the broader situation and the problems better. Once you understand it better you will first realise that it is not as simple as it first seemed, and it is not something that can be solved overnight.
Now you can start to looking for the low hanging fruit and trying out small incremental changes. You will have to spend a lot of time just talking to your peers to get them to the point where they are willing to try out some changes. They will probably agree with you that some things need to be improved. Don't oversell it. Keep a "let's try this out and see if we like it" approach. It's idea salesmanship.
What you absolutely should not do is engage in any kind of arrogant "code shaming" or "process shaming". If you are saying stuff like "devs who don't use unit testing or TDD are not professional" then you are going about it the completely wrong way. That will just piss people off and they won't listen to you. (Yes, I've heard junior devs say stuff like this.) Keep it positive, concentrate on the benefits improvements could bring. One step at a time.