I love working with earlier career engineers but their code isn't known to always be very high quality. How does that work on GitStart?
I love working with earlier career engineers but their code isn't known to always be very high quality. How does that work on GitStart?
We are not fully there yet, but you can see from the Open Source PRs above that its good enough that this can make an in-house team more productive than the default.
Biggest part that makes it work are enabling multiple devs to review each other, solid QA and dev environments to reduce hand-holding and a community to grow and learn from.
Larger corps like Google already have this infra setup, but most teams cant afford to build it internally.
It got merged so clearly the devs find value in the work but I wouldn't call that production ready.
We first got the more experienced junior on the repo review others. Later on, we started to enable multiple devs to work on the same PR initially, review each other and best one sent back
And with GitSlice, we have been able to take very large codebases and slice it to a smaller repo that is much easier for juniors to work on.
So now we get teachers and seniors to train juniors, but they are not in the loop of the PR execution anymore.