At my current and previous jobs, I was given a brief overview of what the whole application did and then a bit on naming conventions and how this particular team seperated the various layers, and then I was thrown in the deep end with my first issue in the ticket management system. It was something that had already been analysed by someone more experienced with the code base, and they told me that they expected me to harass them for help all day.
At my current job, we're all remote workers, so they made a special effort to all be together and available for that first week.
Obviously this works for a new hire who is already very experienced in the language and tools, skilled in the art of software archaeology. It wouldn't work so well for hiring someone less experienced. For that I prefer to do the same brief introduction but then spend the first week pair-programming.
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.
At my current and previous jobs, I was given a brief overview of what the whole application did and then a bit on naming conventions and how this particular team seperated the various layers, and then I was thrown in the deep end with my first issue in the ticket management system. It was something that had already been analysed by someone more experienced with the code base, and they told me that they expected me to harass them for help all day.
At my current job, we're all remote workers, so they made a special effort to all be together and available for that first week.
Obviously this works for a new hire who is already very experienced in the language and tools, skilled in the art of software archaeology. It wouldn't work so well for hiring someone less experienced. For that I prefer to do the same brief introduction but then spend the first week pair-programming.