Books that I have read and liken which may interest you are:

1. Pragmatic Thinking and Learning: Refactor Your Wetware ^[1] by Andy Huny
2. Clean Code ^[2] by Robert Martin
3. The Productive Programmer ^[3] by Neal Ford
4. 97 Things Every Software Architect Should Know ^[4] by Richard Monson-Haefel

Also worth considering is Domain-driven design ^[5] by Eric Evans, this could be written off as a patterns book however I feel it improves the way we look at and think about building OO software.

Also some of the best articles can come from the blogs of the top people in the fields, some of the blogs I follow are:

1. Coding Horror ^[6]
2. Martin Fowler ^[7]
3. Andy Hunt ^[8]
4. codebetter ^[9]
5. Uncle Bob's Software Craftsmanship Corner ^[10]

I'd recommend:

• The Pragmatic Programmer ^[1]
• The Psychology of Computer Programming ^[2]
• Software Craftsmanship ^[3]
• Thriving on Chaos (1st ed.) ^[4]
• Systemantics: How things work and how they fail (1st ed.) ^[5]
• Perfect Software: And Other Illusions about Testing ^[6]

All speak to the nature of the craft of writing code though, in many cases, not actually talking about writing code.

One extra book I'd like to add is Ed Yourdon's " Decline and Fall of the American Programmer ^[7]". The main content of this book is almost completely out of date but the appendix "The Programmers Bookshelf" is worth the price of admission alone. It is a list of books that goes beyond coding and testing along with an essay where Ed picks out many, but not all, of the books and talks about why you should read them.

This was the essay that turned me on to Fred Brooks's book along with Gerry Weinberg's Psychology book mentioned above.

And you can buy a copy of Decline and Fall for 0.01c second hand now!

You might also like to listen to Peter Coffee's Agile 06 keynote address where he relates his choice of "must have" books back to the Agile Manifesto ( mp3 ^[8]). An interesting worthwhile way to pass an hour.

I found these interesting ;I hope you too ,will find interesting

1.Articles by Paul graham ^[1]
2. Coders at work ^[2] by Peter Seibel
3. Joel On Software ^[3]
Edit: I searched SO, i found these links.You must see these links.
One ^[4]
Two ^[5]

I also agree that Code Complete ^[1] is a good one. I found it helpful in identifying the pieces of the coding craft - what steps are involved and what the best practices are.

I just finished Dreaming in Code ^[2] and found it it be a great on-the-ground account of what happens in the life of a software project. It speaks about many (most?) of the major ideas that have come into play in the world of Software Development, and illustrates them with some vivid (and sometimes painful) examples from the real world.

Last one I'd point out is Peopleware ^[3]. It focuses on managing coders and how to get the best out of them. It smells a bit like the 70s, but still has some valuable insights. It's one of the few books I've seen Joel Spolsky recommend himself.

Notes on the Synthesis of Form ^[1], by Christopher Alexander, an awesome book about the process of design. Not so well known as Alexander's books on patterns, this book is a great eye opener.

A great non-software pattern catalog: Organizational Patterns of Agile Software Development ^[2] by James O. Coplien. This book isn´t about software patterns, is about people, a catalog for creating successful teams. Every manager should read this book!

Domain-Driven Design: Tackling Complexity in the Heart of Software ^[3] by Eric Evans, the most valuable book I found to think about the whole software design process.

Peopleware ^[4] by Tom DeMarco and Timothy Lister "demonstrate that the major issues of software development are human, not technical".

In addtion to "Peopleware" and "Code complete"

• Elements of programming ^[1]
• Best software writing ^[2]
• Beautiful code ^[3]
• Coders at work ^[4]

Code Complete ^[1] is a great one.

On top of the already mentioned Code Complete and Peopleware, I found Programming Pearls ^[1] really interesting. It strongly emphasizes the importance of a good problem definition and the choice of the right tools.

Hackers and Painters: Big Ideas from the Computer Age ^[1] by Paul Graham

The Art of Unix Programming ^[2] by Eric Steven Raymond

It does have some code (but then, so does TMMM), but I think that Steve McConnell's Rapid Development ^[1] is a far better book than TMMM when it comes to the practice of software project management - it's not very philosophical though.

Just about anything by Dave Parnas (the guy who really codified the foundations of software design) or Gerald Weinberg. I especially recommend Weinberg's An Introduction to General Systems Thinking, and Software Fundamentals ^[1], a collection of Dave Parnas' papers.

Waltzing with Bears: Managing Risk On Software Projects - by Tom DeMarco & Timothy Lister

This book does an excellent job covering the foundation of risk management and how current practices pay it lip service. My favorite line in the book is a response to the overbearing business executive who wants a more aggressive schedule,

"I can prove to you that beyond March, every month that this product is not ready to ship will cost this company one-hundred-ten-thousand dollars in lost profit."

Which is met with,

"Well then you obviously started this project much too late. If you'd kicked it off eighteen months ago, we could be shipping now, and all those months of hundred-ten-thousand-dollars' extra profit..."

I love Apprenticeship Patterns: Guidance for the Aspiring Software Craftsman ^[1].

Check it online: http://apprenticeship-patterns.labs.oreilly.com/

One that I just got through reading is The Passionate Programmer ^[1], which has been recommended in some other threads here. I also read Practices of an Agile Developer ^[2] a couple years ago, when I was about to transition from being an integration tester to being a developer, and found it helpful.

And on the web, of course, there are great articles on Joel on Software ^[3] that discuss a developer's approach to work.