More seriously, the more I move forward the more I feel that development should be layered. When you're starting out everything is new and exciting and the more you progress the more you need advanced stuff. But in the end there is not so much funky stuff out there.
So the organization I'm trying to figure right now with my company is having several layers of developers based on their experiences, the front line being juniors doing junior jobs and backed by another line of seniors that teach them how to unlock the funky stuff.
This way seniors are always busy with interesting-ish stuff and juniors are never blocked for a week on stupid stuff.
With interns, that's how.
More seriously, the more I move forward the more I feel that development should be layered. When you're starting out everything is new and exciting and the more you progress the more you need advanced stuff. But in the end there is not so much funky stuff out there.
So the organization I'm trying to figure right now with my company is having several layers of developers based on their experiences, the front line being juniors doing junior jobs and backed by another line of seniors that teach them how to unlock the funky stuff.
This way seniors are always busy with interesting-ish stuff and juniors are never blocked for a week on stupid stuff.
While it makes a lot of sense, it could also be really beneficial for your company to share the knowledge and do pair programming with juniors.
Yeah that's basically the idea. Back-up on specific problems is done through pair programming, this way juniors are always explained the fix