You give them tasks with frames of reference. Not all refactored are monsters. It does require some guidance though that’s kind of the point. These are just so

You give them tasks with frames of reference. Not all refactored are monsters. It does require some guidance though that’s kind of the point. These are just some things I’ve been apart of. I’ve gladly been apart of this before. You can as I said also have them write tests or as others noted have them write smaller features or other things in isolation. Also how green are we talking is another question entirely. Some tasks are better fit for people with maybe practical experience in another tech stack but need to get up to speed in a new language etc. My overall point which may not have been clear is that there is always a way to get an engineer up to speed without killing velocity. It’s a management failure to say you can’t hire junior engineers. It’s one thing to need someone that’s a domain expert, but often I see “senior engineer” === “No ramp time” and I think that’s just a lie management tells themselves to justify not coming up with a good on-ramp plan for new engineers