Let him play in the legacy code. You can just hose him off later before letting him back into the office so he doesn’t track it everywhere.
Unfortunately if you let Junior play in legacy code once, it’ll learn some nasty habits and make more of it from scratch, usually when you’re trying to sleep.
It’s true, spaghettification sauce stains clothes. Best keep Jr out of it entirely.
I don’t want that shit all over me though. That’s why I hired junior!
The leash is good unit testing.
Oh, he’ll just change the unit test if it fails.
Unit tests are there to get an @ignore annotation!
The junior doesn’t know that these aren’t unused functions. They’re load bearing functions.
Neither does the senior
Anymore
Why is the junior dev tied to the other one’s penis?
Bro that’s not where the penis is located on the body
There’s also that long time senior dev who’s overly confident in their abilities and force pushes production breaking code directly to master.
Not for long there isn’t.
Make him unit test it all and then they can do changes that don’t break.
Often enough, the old code is so badly intertwined that it’s impossible to actually test. Those are the moments where all you can do is nuke it from orbit.
