I agree with Rands that the software development world is changing but since that's always been true, I don't find it a a compelling enough reason on its own to keep dirty.

Other reasons to keep your hands dirty include:

1. Respect from the great developers on your team. The incompetent ones won't like it but the great ones will. Of course, I'm assuming you're also a great developer for if you are not, then don't bother trying to be dirty as it will pay off only in derision.

2. It takes one to know one. Think about how you hire great developers. If you weren't one yourself with current skills and experience how could you get a) respect as above b) ask the questions you need to know that you've got a live one and c) be able to correct for dysfunctional team interviews (you know, where you rely on your team to screen candidates yet losers make it through the process anyway because everyone thought that someone else was asking the hard questions) and d) be able to paint an accurate picture for candidates on what is really going on and what real-world expectations are and finally e) be able to competently back-fill yourself or via hiring when your best developer(s) decide to do something new.

3. You really can't judge the quality of the work unless you really understand it. Think about staff reviews for a moment. There's little moral stance to review a developer if you can't judge them as an equal or superior.

4. Your junior people need to know that they can aspire to something larger and still remain engaged and interested in the details.

5. You might change jobs in the future and be expected to a) pass interviews b) create.

Happy dirt.