I think you can cross out the bit you quoted and it still adds up. Whether you're working with the "merely proficient" or "coder deities" you still want to giv

I think you can cross out the bit you quoted and it still adds up. Whether you're working with the "merely proficient" or "coder deities" you still want to give them tasks that will push them to expand their skills, rather than just a never-ending stream of what you already know they do proficiently. I'm not sure how much to generalize beyond that -- you'll want to be sure they're making steady progress and not spinning their wheels, so check in periodically or sort out some other way to know how they're doing. I personally keep a running text file for hard problems I'm figuring out -- tracking research/links, debugging results, POC details, etc., with a "status/do this next" list at the top that I review each time I pick it up again. When I want other people to be able to learn from what I'm doing (i.e., I'm doing something hard but will want others to work on it later), OR track where I'm headed (if they may have input to offer), I do this on a shared wiki page. There are lots of ways to keep that info flowing; just do something so you know ASAP when someone gets saddled with something they hate, don't understand, can't get through, or even find boring.