Suppose you hired a contractor to apply stucco to the walls of your shed.
Now suppose the result was lumpy, uneven, cracking, and had patchy coloring.
I guess you’ll need to bring in a true expert to fix the mess.
Will this expert patch the cracks? Add touch-up paint to hide the splotchy coloring? Add a layer of stucco on top of the uneven parts?
Nonsense! The results would be disastrous. It might work for a while, but you’ll regret it in a few months.
Instead, the expert will remove the existing work and start afresh. The expert will evenly mix new stucco with new paint, apply a perfectly even coat of stucco, and ensure a crack-free result. The finished product will be fabulous! You will be happy — until you realize you missed your budget and missed your deadline because you paid for and waited on the job twice.
If you have junior developers on your team, you can’t ask them to code the whole project on their own without risking a costly disaster. Instead, they must work alongside more experienced developers so that they learn. You can’t hand them responsibilities outside of their limits and expect good results. Instead, trust them with aspects of the project that fit their abilities, stretch their capability bit by bit, and help them grow. You must carefully balance the assignments across the team so that everyone has opportunity to learn, but no one is stretched beyond their limits.
Don’t let junior developers flounder on a project only to bring in more experienced developers later to rescue it. The results will suffer, the costs will go up, and the morale will go down.
gladtocode 