4 ms·
Who maintains the code written by those remote junior devs? If the answer is: the team that owns the project, then effectively, these remote junior devs are pro
by danwee 3y ago
Who maintains the code written by those remote junior devs? If the answer is: the team that owns the project, then effectively, these remote junior devs are producing legacy code the moment they finish their job. If the answer is: the remote junior devs, then that implies you need to hire them again for that... so what's stopping you then from hiring junior devs full-time at all?
- wutania 3y agoi would say it should be the engineer who was owning the initial issue, and then reviewed/ merged the PR to own the code. it should be them on gitblame anyways as a co-author once a gitstart PR is merged i would think gitstart as an extension to engineers themselves instead of working in silo disclaimer: i used to work at gitstart
- hzia 3y agoWe have seen that GitStart works best when its meant to accelerate an in-house team, instead of being a member of your team. As a result, the end team that uses GitStart has full ownership of all code that gets merged. However you can assign future bug fixes and maintenance work back to GitStart.
- hzia 3y ago> what's stopping you then from hiring junior devs full-time at all? There is nothing stopping devs from getting recruited directly, in-fact we want that to happen! Its a major success story for us when devs get hired, ideally back to our customers :)