[lug] software development/engineering books

[Tkil]

i chatted with someone briefly after the meeting about useful
references for software engineering, design methodologies, teamwork,
etc.  here's a list of my favorites (efm had a few more; she should
add them onto the mailing list).

books that cover the overall process:

Brooks, Fred.  The Mythical Man-Month (Silver Anniversary Ed).
   ISBN: 0-201-83595-9

   absolutely essential.  the 25th anniversary issue added in his
   famous "no silver bullet" article, as well as his observations on
   how things (haven't) changed since the original came out.

DeMarco, Tom and Timothy Lister.  Peopleware (2nd Ed).
   ISBN: 0-932633-43-9

   one of the best works on the sociological side of software
   development.  the 2nd edition again adds insights from the 10 years 
   between the two editions.

McCarthy, Jim.  Dynamics of Software Development.
   ISBN: 1-55615-823-8

   it's from microsoft press, but don't let that stop you.  :)  it has 
   a lot of aphorisms about specific issues that people get stuck on
   during the development process.  as such, it is often good for a
   quick read of a page or two, or glancing through for some ideas
   about particular problems.

Yourdon, Edward.  Death March.
   ISBN: 0-13-748310-4

   he actually has quite a few books out (i also have his "the decline
   and fall of the american programmer" and then "the rise and
   resurrection of the american programmer").  they're almost light
   fare, but they were the first books i remember reading that dealt
   with interesting pragmatics (as apposed to trying to build an
   "ideal" team/environment).  things like: "good enough" software, as 
   well as what can be salvaged from a dying project (which is the
   topic of this one, "Death March").

books about particular design methodologies:

Beck, Kent.  Extreme Programming Explained.
   ISBN: 0-201-61641-6

   describes a lightweight, responsive methodology.  particularly
   applicable to smaller organizations, whether they're trying to sell 
   a product to the public at large or (more specifically) if they're
   trying to support a particular customer/group's needs.

[yes, there are a lot more here.  efm mentioned some useful web sites
that help navigate all this.]

finally, don't forget books about improving your skill as a program-
mer.  getting better at the low- to medium-level stuff should increase
your precision as an estimater and designer.

anyone else care to pitch in?  (i feel i had more books, but i can't
seem to find them offhand.  alas.)

t.