That's a very pessimistic view of software development. The thrilling part of the work is building things and seeing people use them. That's what it's all about.
There is always grunt work, but instead of "battling" javascript and CSS you could use the opportunity to learn more about browsers, interface design, etc. Channel the frustration into building new, better frameworks, or helping improve the existing ones. There are plenty of opportunities to exercise your CS education in fast-growing or large-scale businesses. And for all I know, solving problems in the kernel or coding OpenGL could be even worse.
> And for all I know, solving problems in the kernel or coding OpenGL could be even worse.
For me, solving problems in the kernel is immensely more interesting and rewarding than fixing the n-plus-oneth CSS aligning bug. It also comes with the added advantage of using real development tools instead of nuts and bolts that barely help you.
Apples to oranges. My point is, writing OpenGL code or fixing driver compatibility issues can be just as boring. CSS is not exactly programming anyway.
On tooling, take a look at current webkit/FF/Opera inspectors, TraceGL, TernJS, the upcoming IE11 developer tools and TypeScript. You'll be surprised.
There is always grunt work, but instead of "battling" javascript and CSS you could use the opportunity to learn more about browsers, interface design, etc. Channel the frustration into building new, better frameworks, or helping improve the existing ones. There are plenty of opportunities to exercise your CS education in fast-growing or large-scale businesses. And for all I know, solving problems in the kernel or coding OpenGL could be even worse.