Edit: Actually, there are no CRUD jobs in kernel development. There aren't CRUD jobs in a lot of fields. There aren't any CRUD jobs in database design and development. There aren't any CRUD jobs in compiler design. Any argument to the contrary betrays a fundamental ignorance of what CRUD means[1].
[1] http://en.wikipedia.org/wiki/Create,_read,_update_and_delete
A baker does CRUD with bread, a surgeon does CRUD with people's organs, a dentist does CRUD with teeth, and a physicist simply does low-level CRUD at an atomic level.
By stating it this way it sounds simple, but you know, the devil is always in the details...
It's not about splitting hair but having the domain knowledge in addition to coding skills.
That one I would have to say is pretty spot on, domain knowledge adds a lot of value to a developer.
As for the it's all CRUD, I think that is a oversimplification at best. Software development can be rolled up into patterns and best practices but to oversimplify it down to it's all CRUD is a little beyond the reality of the duties of the role.
Anytime you start doing something novel, you are no longer a software engineer; you are a computational biologist, quant, game designer or computer scientist. It's not about splitting hair but having the domain knowledge in addition to coding skills. (Because let's not kid ourselves, programming is easy) If people insist on elevating themselves, then it's their prerogative. But since the market is right and is programming skills are becoming a commodity, I would rather be rich than popular.