A see a lot of ppl talking about shit junior devs do, this is good lets me know wat not to do

📌

Use google and your brain.

📌

devRant in general has been a how not to fuck up manual for me, and a pretty good one at that.

I think if you make your project junior proof, it should be a good and efficient learning process along with a low risk one. Even a good reminder to senior to not create shit as well. Think twice about using your admin rights.

Source control: disable commiting on main branches, PR with reviews for merges.
Code: development guidelines, CI, best practices, document the general work process for fuck sake.

With lazy senior devs comes confused juniors. Put yourself in their shoes, you were a junior before.

wk235 - Advice you've given to junior devs

https://devrant.com/search/...