There's something I actually don't understand: what else would they do if not contribute right away to the project? They're junior, sure, but you hired them, and if not for working on your projects, then what for?
Give them tasks adapted to their skills, that will make them explore the code base and discover the contribution process (we have mandatory code reviews for example). Code review or whatever you put in place should prevent them doing any harm, and make them learn and improve their skills, from day/week one.
Fwiw, we do have a few training sessions (approx. 4 days in total) about our internal processes, how to use git, how CI and code reviews work, and a few sessions on the basics of HTTP, SQL, and frontend development (things they'll probably use whichever the project and team). Those come while they're already in their team so they can directly relate what they learned to what they're tasked to do.
Ha. Yeah, honestly I have seen a lot of cases where the junior dev is just thrown in a random useless task to Train Them (TM) so they spend a month writing code that will go straight to the trash, or reading stuff... but as you mention, it doesn't work that way! You cant expect junior engineers to grow if you don't let them learn with their team.
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
There's something I actually don't understand: what else would they do if not contribute right away to the project? They're junior, sure, but you hired them, and if not for working on your projects, then what for?
Give them tasks adapted to their skills, that will make them explore the code base and discover the contribution process (we have mandatory code reviews for example). Code review or whatever you put in place should prevent them doing any harm, and make them learn and improve their skills, from day/week one.
Fwiw, we do have a few training sessions (approx. 4 days in total) about our internal processes, how to use git, how CI and code reviews work, and a few sessions on the basics of HTTP, SQL, and frontend development (things they'll probably use whichever the project and team). Those come while they're already in their team so they can directly relate what they learned to what they're tasked to do.
Ha. Yeah, honestly I have seen a lot of cases where the junior dev is just thrown in a random useless task to Train Them (TM) so they spend a month writing code that will go straight to the trash, or reading stuff... but as you mention, it doesn't work that way! You cant expect junior engineers to grow if you don't let them learn with their team.