|
|
|
|
|
by abatilo
1047 days ago
|
|
Something about promising high quality production code while also emphasizing the growth of junior engineers feels inverted. 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.