[Humdeee]

> Nobody is going to do the boring work first and leave the interesting stuff sitting around just waiting for a new hire!

I don't know about this... we usually give the exciting stuff to the more junior or co-op/intern hires. The boring work has usually been the most important work from my experience. There is an inherent risk with the exciting and unknown ending in a flop.

[mfoy_]

Thinking about it, same here. If there's some tedious but critical 10-min sysops task, I'll usually just do it rather than try to pawn it off on a junior coworker. But if we want to do something exciting, such as set up a new piece of flashy tech for evaluation, that will usually fall to a junior resource to 1) help them grow and learn and 2) because if they fail spectacularly there was nothing important riding on it.