http://www.realtransit.org/nec7.php has some interesting charts and analysis of the speed limits on the various segments of the Northeast Corridor. Note that the values shown are not necessarily what it achieves in practice, but there's seemingly potential to address that via operational changes and small, targeted capital spending.
Not a book, but https://hackattic.com/ is in this vein. It's not the standard coding challenge website it may seem to be, instead a collection of small projects representative of the core ideas underlying "real world" systems. It provides just enough scaffolding and direction to get one started down the path of autodidactic exploration; satisfying and enlightening without being frustrating.
Summit and Sierra are two planned DOE machines with hardware developed in collaboration with IBM and Nvidia. They're slated to feature Volta GPU, a generation past P100's Pascal.
Another worthwhile list to look at is the Green500 [1], which ranks machines based on MFLOPS/Watt. With the exception of a few GPU and Xeon Phi heavy machines at the top, the high end is dominated by IBM's Blue Gene machines.
The arrow operator and identifiers with leading underscores seem to be glossed over or skipped fairly often in education. It's intimidating to look at code that uses them if you don't know what they are.
CDARS is a simplified way to do that with CDs, essentially distributing amounts past the FDIC limits into different banks behind the scenes, so that you only have to deal with one account, but get insurance on the entire amount.
Michaek Spivak's "Calculus" is pretty great for learning real analysis. The other canonical text is "Principles of Mathematical Analysis" by Walter Rudin, which I've never used, but is purported to be of the same quality.
I used this template when I redid my résumé a few months back. I like how it does away with those extraneous bullets and lines found on many résumés; it is uncluttered, elegant, and very readable.
Fresh off an internship myself, I can attest to the benefit of having a side project. Primary projects often do get hung up, and with nothing else to work on, interns are left venturing off into places unknown. Some predetermined side projects would prevent a lot of downtime, something that's vital when one only has ten or so weeks to work.
Ultimate Ears (now a subsidiary of Logitech) is pretty well known for their custom in-ear monitors. Prices go as low as $399, not ludicrously expensive. I've never used them personally, but others seem to be pretty well chuffed by them.
Yeah, I mean a join with a timeout, and it is indeed not too much of a hassle to work around, but it's more the principle of not having an innate timed join in POSIX Threads.
The Open Group published their rationale for not including a timed version of join, stating, "the working group ultimately rejected [adding a timeout to] pthread_join() since both that interface and a timed variant of that interface are non-minimal and may be implemented as a function. See below for a library implementation of pthread_join()."