Re: other suggestions?
I used to read many of the type of non-fiction books that are listed here. However, after reading The Passionate Programmer, it gave me the right kick in the head to put things in perspective. Consider the following quotes:
"Many of us are drawn to the IT industry because things are always
changing. It's an exciting and fresh work environment. There's always
something new to learn. On the flip side, though, is the disheartening
fact that our hard-earned investments in technology-related knowledge
depreciate faster than a new Chevy. Today's hot new item is tomorrow's
obsolete junk with a limited shelf life."
"Unless you're really lucky, you're probably not getting paid to be smart.
And you aren't getting paid to be a leading expert in the latest technologies.
You work for an institution that is, most likely, trying to make
money. Your job is to do something that helps the organizationmeet that
goal. All of this careful thought and preparation has made you ready to
show up at work and start kicking ass for your company."
"One of the many sources of controversy around the Extreme Programming
movement is its initial assertion that teammembers should work
no more than forty hours per week. This kind of talk really upsets
slave-driving managers who want to squeeze as much productivity as
possible from their teams. It even kind of upset programmers themselves.
The number of hours worked continuously becomes part of the
developer machismo, like how many beers a frat boy can chug at a
The sobering thruth about many of us in the IT field is that much of the extra effort we put forth gaining in depth knowledge on topics such as IPv6 for example, goes beyond the tye of knowledge that most companies are willing to pay for. They may welcome it, but it is often more than they need to reasonably (not speaking perfectly) keep their businesses running.