The Abbot project

• How to be a Programmer: A Short, Comprehensive, and Personal Summary, Robert L Read
  Not short, but excellent distillation of one man's programming wisdom. Covers handling difficult colleagues, management, coding, optimizing and the difficult task of debugging.
  
• The Art of Unix Programming, Eric Raymond
  More than just a programming guide, an exposition of a design philosophy -- the Unix way. Encyclopaedic in ambition and scope.
  
• Producing Open Source Software, Karl Fogel
  A guide on how to run a successful open source software project. I like his introduction: "Most free software projects fail.
  We tend not to hear very much about the failures. Only successful projects attract attention, and there are so many free software projects in total that even though only a small percentage succeed, the result is still a lot of visible projects. We also don't hear about the failures because failure is not an event. There is no single moment when a project ceases to be viable; people just sort of drift away and stop working on it.".
  
• Worse is Better, Richard Gabriel
  Still provocative and topical. The concept known as "worse is better" holds that in software making (and perhaps in other arenas as well) it is better to start with a minimal creation and grow it as needed. Further debates on "worse is better".
  
• Being A Better Programmer, Danny Burbol
  Advice written from a game programmers perspective. I don't quite agree with his opinions on documentation (I think you need to think of documentation as teaching, not making notes; in a large project, there should be some programming overviews and tutorials so people can kickstart without bugging you), but overall it's good advice.
  
• Little Nybbles of Development Wisdom, Terence Parr
  What one man learnt over the course of a 3 year software odyssey - a bit too preachy for me (some of the advice seems specific to his project) but still interesting.
  
• How To Write Unmaintainable Code, Roedy Green
  Roedy is a dangerous man :)
  
• The archives of Joel On Software are a good read.
  
• Alan Cox, Linux coding master, on writing better software.
  

Software Methodologies

• Nasa's Sofware Engineering Laboratory Methodology
  I highly recommend reading the Manager's handbook (PDF). There are some incredible metrics inside. For example, here's their productivity estimate for experienced programmers (a 10 year veteran is supposed to be 5 times more productive than a freshman):
  
  

  Years Experience	Work Required
  10	0.5
  8	0.6
  6	0.8
  4	1.0
  2	1.4
  1	2.6

  
  
• Agile Software Development
  Agile is an umbrella for a wide range of ways to write software quickly.
  
• Rapid Application Development
  RAD made CASE tools fashionable, until everyone reverted to text editors for HTML and javascript.
  
• I have always believed in the Spiral Model.
  
• Extreme Programming
  XP is a well-known Agile methodology. Very controversial - here's a counter-point.
  
• Great Hackers, Paul Graham
  A hacker manifesto. Anti-methodology. Show's how smart people can be a pain in the $#@^&@!
  

Some of the programming articles could have been placed under software methodologies too.

Software Economics

• The Economics of Software, Bryan Cantrill
  A supply and demand analysis of software for the layman.
  
• The Business of Software, Eric Sink
  An excellent collection of essays on running a software business and making the right decisions.