For more fiction, how about The Curious Incident of the Dog in the Night-Time by Mark Haddon, which Publisher's Weekly summarized as "Christopher Boone, the autistic 15-year-old narrator of this revelatory novel, relaxes by groaning and doing math problems in his head, eats red-but not yellow or brown-foods and screams when he is touched." It has math problems scattered throughout.

Do what I did and take a summer off.

Actually, I did a co-op (for which I received somewhat useless credit from my university) which sent me to Europe and Africa to do some computer work. They were specifically looking for a single person to do this, and it wasn't a common opportunity in my experience, but I jumped at the chance.

The following summer, I took part of the summer off from my required courses. For some courses, our short summer semester was divided in two, and in the first 6 weeks I took an outstanding gen-ed course, and in the second 6 weeks I went on a study abroad trip to Italy and studied Italian and Renaissance art, neither of which I had studied before or had a prior interest in. We studied at an Italian University from Monday to Friday (sometimes Thursday) and traveled around on the weekends, and then the last week was spent traveling full time.

That was one of the most fulfilling experiences of my life, and the irrelevant-to-my-degree but relevant-to-my-travels courses served as a nice break from my beloved 1's and 0's and greatly enriched the experience.

In short, I highly recommend finding a way to study abroad, even if it delays your graduation briefly.

You will need to do some tuning with a tool like Gimpel's PC-Lint, so it's best to use it from the get-go rather than try to start linting part way through or at the end of your project. Then you do some initial setup and make minor tweaks as you go, so the tuning process is not at all painful. Many tools, like PC-Lint, also integrate into IDEs like Visual Studio, and some have free add-on programs like ALOA (http://pera-software.com/htm/english/aloa.htm) which analyzes the output of PC-Lint to generate some metrics for the quality of the code.

I have found such tools to be invaluable. I had code like this:
class Lock {/*...*/};
void Foo( Mutex& m )
{
Lock(m);
// ...
}

This is valid syntax, but I intended to use that lock instance for the duration of the function, so the first line should have read "Lock lock(m);". Multithreading is tricky enough, and I looked at the real code for a long while, reading right over this bug. PC-Lint found it for me right away (thankfully, it was already tuned, and I should have been using it before running my code).

But even though PC-Lint is pretty good, it ain't perfect. I have found that it has some trouble with advanced C++ templates (e.g., policy-based design). I have submitted bug reports for many of these problems, and they do seem responsive in working them in to the patches.

Finally, here's an article from 2006 discussing the available static analysis available tools for C, C++, and Java and describing how and why to integrate it into your development process.