best books to read for software engineer

Have you ever looked at a class, or a method that seems to work fine but it just doesn't "feel" right?
For some reason it seems as if that method or class may be hard to debug in the future or that
the code is hard to understand. Or have you gone back to a class file you wrote months ago and you spend an
awful lot of time trying to figure out what the heck is going on with that class file? Maybe the methods in
the class are spaghetti like in nature, or maybe the names of your methods don't have a very good description
so it's hard to figure out how everything ties together. I have had this problem. This book will teach you
how to get out of those habits. You will learn what a solid class or method looks like. You will learn
how properly naming your classes and methods can greatly reduce complexity in the long run. Everything is backed by hard evidence.
I should also mention that this is just one chapter in this wonderful book.

This book really drills down proper programming practices. A lot of times you may read a passage and think to yourself
"Well, of course!"... but then you realize you don't practice what's contained in the passage you just read.
This book is great for both new programmers and experienced programmers alike. New programmers benefit greatly because
they will learn how to construct software properly without having to go through all of the hoops. Experienced programmers
will also learn a great deal, as well as be reminded that some of the habits that they've developed over the years can hinder
production and cause software development to become more complex than it really is.

Steve writes in a very clean style. It's very easy to read. You don't need to memorize anything in a book like this,
instead, you just need to gain an understanding of the concepts he brings forth. After reading this book I definitely
followed a lot of his advice. When I build a new class, method or what-have-you I get a certain feeling of when
it seems right and when something seems wrong. I am now much better at analyzing my code and figuring out
what doesn't seem correct and I take the advice I learned in this book to help me to figure out -
and correct the problem. After reading this book I feel like a lot of my rough edges as a developer have been rounded out.
I feel as if I gained a year's worth of experience just by reading this book.

This book is friendly for any software developer. The concepts he presents apply to all languages.
This is a book that teaches you how to think about programming better and how to construct good solid code.
This is one of the best books I've ever read. If you're even thinking about buying this book, then buy it.