3 ms·
I've seen a team of 5 junior devs on an existing product outpace 10 senior devs on a team to replace that product from scratch for 3+ years. A third team, of l
by jabart 8y ago
I've seen a team of 5 junior devs on an existing product outpace 10 senior devs on a team to replace that product from scratch for 3+ years.
A third team, of like 3 devs, made a proof of concept using the Strangler pattern and just a simple API to interact with the existing database within a year and took over the "rewrite project".
- m0zg 8y ago5 devs will nearly always outpace 10 if they have to work on the exact same piece of code. You gotta break it up into teams of at most 4, with as little overlap as possible. Communication doesn't scale.
- bobthepanda 8y agoThe other problem is that 10 senior devs sounds like too many cooks and egos in one kitchen. Junior devs have less experience, but that also can mean less rigidity and a willingness to explore new options.
- jspash 8y agoSure, junior devs will usually outpace senior devs (especially looking at LOC). But in the end, did they produce robust, reliable, fault-tolerant code that is easy to understand, extend and most importantly delete? I'd like to hear more specifics on this project. Especially why if junior team A and senior team B were already working for 3 years, why was team C introduced? Did they save the day? I'm really curious about the final outcome and any learnings you might have had.