<?xml version="1.0"?>
<?xml-stylesheet type="text/xsl" href="book-std.xsl"?>
<!DOCTYPE books SYSTEM "books.dtd" >
<!-- Categories are defined in categories.xml -->



<books>
<book status="new" scmsite="no">
	<title>Pragmatic Thinking and Learning</title>
	<isbn>1934356050</isbn>
	<authors>Andy Hunt</authors>
	
	<imageURL>cover/1934356050.jpg</imageURL>
	
	<categories>
		<category>PEOPLE</category>
		<code>Systems</code>
		<code>CREATE-SOLVE</code>
		
	</categories>
	
	<comments>
A well written, entertaining, guide to tools and techniques to help you be a better engineer. While many of the examples are geared towards software developers, anyone who wants to learn how to use their time (and energy) more effectively will benefit from reading this book. This book is a great mix of background material to help you understand how you learn, resources to enable you to learn more, and techniques to help you practice right away. This book will be one I refer to often, and is a great companion to Getting Things Done, and Becoming a Technical Leader.
	</comments>
	
		<seeAlso>
 <isbn>0932633021</isbn>
 <isbn>093263365X</isbn>
	 </seeAlso>
</book>

<book status="new" scmsite="no">
	<title>Effective Java (2nd Edition)</title>
	<isbn>0321356683</isbn>
	<authors>Joshua Bloch</authors>
	
	<imageURL>cover/0321356683.jpg</imageURL>
	
	<categories>
		<category>J2EE</category>
		<code>Systems</code>
		
	</categories>
	
	<comments>
As Java evolves and there are more ways to do things, it's getting more important to learn which idioms to use to benefit from library and language features. Effective Java is a well written book  that will help new programmers learn how the right way to solve problems, and provide experienced programmers with a refresher course so that they can break out of bad habits, and make use of new library and language features. Read or skim the book from start to finish to get a sense of what's there, and keep it nearby when you are coding as a reference.
	</comments>
	
	
</book>

<book status="new" scmsite="no">
	<title>Weinberg on Writing: The Fieldstone Method</title>
	<isbn>093263365X</isbn>
	<authors>Gerald M Weinberg</authors>
	
	<imageURL>cover/093263365X.jpg</imageURL>
	
	<categories>
		<category>PEOPLE</category>
		<code>CREATE-SOLVE</code>
		
	</categories>
	
	<comments>
This is an inspirational and practical book that will both help you be a better, more productive writer and make you want to write. Weinberg explains timeless techniques you can use to collect and organize your ideas effectively when you are writing about a topic you care about. Jerry Weinberg's books have had a positive influence on my life as a technologist and manager, and with this book, he is now inspiring me to be a better writer.  If you  are a writer, or want to be one, you will want to read this book once for inspiration, and refer to it again later for it's exercises and advice.
	</comments>
	
	
</book>

<book status="new" scmsite="no">
	<title>Practices of an Agile Developer: Working in the Real World</title>
	<isbn>097451408X</isbn>
	<authors>Venkat Subramaniam and Andy Hunt </authors>
	
	<imageURL>cover/097451408X.jpg</imageURL>
	
	<categories>
		<category>SYSTEMS</category>
		<category>AGILE</category>
		
	</categories>
	
	<comments>
A Pragmatic, method agnostic, guide to the essential practices for an agile team. The book covers the whole lifecycle form planning  to design and coding, showing you how to balance the agile dogma with practical considerations. The book also addresses common misconceptions about agile practices. People new to agile will benefit from the book, but those who have been working using an agile method will get a lot from a fresh look at why they are using agile practices.
	</comments>
	
	
</book>

<book status="new" scmsite="no">
	<title>Implementation Patterns</title>
	<isbn>0321413091</isbn>
	<authors>Kent Beck</authors>
	
	<imageURL>cover/0321413091.jpg</imageURL>
	
	<categories>
		<category>SYSTEMS</category>
		<category>AGILE</category>
		
	</categories>
	
	<comments>
The title is misleading, as the book really isn't a Patterns book, and it's not a detailed handbook. This is a good terse summary of principles to apply when writing code that others will need to work with. While the book is light on details or examples, reading it can help you consider what coding and micro design conventions to apply to make your code more readable.  This is a good companion to Bob Martin's Clean Code as Martin and Beck, excellent coders both, sometimes make opposite recommendations about the same situations. These contrasts drive home the point that rules for good code need to be considered, not just accepted without thought.
	</comments>
	<seeAlso>
	<isbn>0132350882</isbn>
	 </seeAlso>
	
</book>

<book status="new" scmsite="no">
	<title>Clean Code</title>
	<isbn>0132350882</isbn>
	<authors>Bob Martin</authors>
	
	<imageURL>cover/0132350882.jpg</imageURL>
	
	<categories>
		<category>SYSTEMS</category>
		<category>AGILE</category>
		
	</categories>
	
	<comments>
The book is a great guide to the basic qualities of good code. While many of the guidelines were familiar, reading the book helped me reconsider some rules that I had followed out of habit, but which no longer make sense. Like many good books even if you know and agree what it says, reading the book can help you explain "the obvious" to others. Clean Code has all the qualities of a classic book.

Bob does not just a list of  rules for "good" code. He explains why following the rules makes for better code, and provides several examples of how following the rules make arguably good code (like JUnit) better. Buy this book if you write code or manage people who write code. This is a must read if you are developing a coding standard for your team. Even if you don't accept all of Bob's guidelines, reading this book  will help you think about what standards make sense for your team. 
	</comments>
	<seeAlso>
	 <isbn>0321413091</isbn>
	 </seeAlso>
	
</book>


<book  scmsite="no">
	<title>Prototype and script.aculo.us: You Never Knew JavaScript Could Do This!</title>
	<isbn>1934356018</isbn>
	<authors>Christophe Porteneuve </authors>
	
	<imageURL>cover/1934356018.jpg</imageURL>
	
	<categories>
		<category>SYSTEMS</category>
		<category>J2EE</category>
		
	</categories>
	
	<comments>
This book compliments the online resources nicely, explaining not just what to do, but why, and how to do things best. This book does an excellent job of straddling the line between reference and introduction. The writing style is readable enough that you can read a few chapters just to get a sense of what to do, while at the same time, terse enough that you can find what you need quickly.
	</comments>
	
	
</book>

<book  scmsite="no">
	<title>What Every Body is Saying: An Ex-FBI Agent's Guide to Speed-Reading People</title>
	<isbn>0061438294</isbn>
	<authors>Joe Navarro</authors>
	
	<imageURL>cover/9780061438295.jpg</imageURL>
	
	<categories>
		<category>PEOPLE</category>
		<category>ORGS-METHODS</category>
	</categories>
	
	<comments>
This book can not only help you to be more aware of when to probe further about whether what someone says is inconsistent with what they may be feeling, but it also can help you be more aware of the messages you may be sending by your gestures, posture, etc. One of the things I like most about this book is that the author sets the expectation that you won't be able to know the "truth" based only on body language but that awareness of body language will help you to understand when you should be paying attention to other details of your interaction with someone. Anyone who works with people, especially in a customer-facing role, would benefit from reading this book.
	</comments>
	<seeAlso>
	 <isbn>0932633021</isbn>
	 </seeAlso>
	
</book>

<book  scmsite="no">
	<title>Manage It! Your Guide to Modern, Pragmatic Project Management</title>
	<isbn>0978739248</isbn>
	<authors>Johanna Rothman</authors>
	
	<imageURL>cover/0978739248.jpg</imageURL>
	
	<categories>
		<category>AGILE</category>
		<category>SYSTEMS</category>
				<category>ORG-METHODS</category>
	</categories>
	
	<comments>
Manage It! will help you understand how to manage projects effectively, taking into account the needs of the people working on the project as well as the needs of the business sponsors. In this regard Johanna Rothman follows in the steps of authors like Jerry Weinberg by showing you how to set up a project environment that helps software developers be more effective and thus be better able to deliver value to their customers. This book has pragmatic advice on how to make progress and issues visible, how to plan a project, and most everything else you need to help a project come to a good conclusion. This book is unique in that while it discusses the benefits of agile lifecycles, it shows you how to make progress in a variety of software lifecycles, and gives advice on when to use the various lifecycles she discusses. Buy this book if you want to  be a more effective project manager (or technical lead who works with project managers), or if you want to be more agile but are not sure how.
	</comments>
	<seeAlso>
	<isbn>0932633420</isbn>
	    <isbn>073561993X</isbn>
	    <isbn>0130086959</isbn>
	</seeAlso>
</book>

<book  scmsite="no">
	<title>The Inmates are Running the Asylum</title>
	<isbn>0672326140</isbn>
	<authors>Alan Cooper</authors>
	
	<imageURL>cover/0672326140.jpg</imageURL>
	
	<categories>
		<category>AGILE</category>
		<category>SYSTEMS</category>
		
	</categories>
	
	<comments>
This a classic book that anyone who build computer systems should read. Some of the specific examples are dated, though many caused me to nod in acknowledgment, especially his observations about alarm clocks and TV remotes,  Inmates describes goal directed design, the concept of Pesonas, ideas which, whether they make sense for your project are not, are ones that you should be aware of. This book also explains what "polite software" is and emphasizes the market advantages to good interaction design. Even if this book doesn't change the way  you work, it will help you think about the relationship between interaction design and programming. Among the interesting points Cooper makes are Customer Driven isn't aways the best model (customer influenced is better), and neither is Engineering Driven; software designers should go beyond customers say they want and help them to understand what they need. There were a few things towards the end of the book that struck me as just wrong. For example Cooper says that most developers don't believe that they are the best people to test their code. Most Agile software developers would challenge that point. Agile developers would also challenge the recurring theme that the engineering team can't make the leap to understanding the customer enough to build good interaction design. He ignores the value of a specializing generalist, which is an important concept in today's projects.  Regardless, this is a book that anyone building software systems should read, if only to understand the concepts underlying interaction design.  
	</comments>
	<seeAlso>
	   <isbn>0201924781</isbn>
	    
	   
	</seeAlso>
</book>


<book scmsite="no">
	<title>Implementing Lean Software Development</title>
	<isbn>0321437381</isbn>
	<authors>Mary and Tom Poppendieck</authors>
	
	<imageURL>cover/0321437381.jpg</imageURL>
	
	<categories>
	<category>ORGS-METHODS</category>
		<category>AGILE</category>
		<category>SYSTEMS</category>
		
	</categories>
	
	<comments>
Implementing Lean Software Development is an essential resource if you want to understand the value of lean software development. It explains the theory of lean manaufacturing and how it applies to software development. It contains practical advice for implementing Lean and anecdotes to help you to understand the value of Lean. This is a great addition to the library of any agile developer or project manager.
	</comments>
	<seeAlso>
	   <isbn>0321150783</isbn>
	    <isbn>073561993X</isbn>
	   
	</seeAlso>
</book>


<book  scmsite="yes">
	<title>Wicked Problems, Righteous Solutions</title>
	<isbn>013590126X</isbn>
	<authors>Peter DeGrace and Leslie Hulet Stahl</authors>
	
	<imageURL>cover/013590126X.jpg</imageURL>
	
	<categories>
	<category>ORGS-METHODS</category>
		<category>AGILE</category>
		<category>SYSTEMS</category>
		
	</categories>
	
	<comments>
A Wicked Problem is a problem where some of the solution space lies within the problem space; the problem is only fully understood after it is solved. Thsi book describes how many programming problems fall into the catgegory of wicked problems and how waterfall softwarae development practices are not well suited to these kinds of problems.This book explains how agille approaches are more suited for many software development projects. In addition to all of this, this book had many excellent references.
	</comments>
	
</book>
<book  scmsite="yes">
	<title>Practical Perforce </title>
	<isbn>0596101856</isbn>
	<authors>Laura Wingerd</authors>
	<website>
		<url>http://www.perforce.com/</url>
		<description>Vendor Web Site</description>
	</website>
	<imageURL>cover/0596101856.jpg</imageURL>
	
	<categories>
	<category>SCM</category>
		
	</categories>
	
	<comments>
This is a how-to guide for doing Software Configuration Management with Perforce. In addition to describing hpw the various commands work this book helps you understand how to structure your version control system to use Perforce effectively. This book describes not only how to create branches, but why, and what policy to have on the branch. The Channelling the Flow of Change chapter is a great introduction to change management concepts in general. Buy this book if you are using Perforce as your SCM solution, or even if you are evaluating multiple solutions, and Perforce is a candidate, as this book will help you understand how to structure your environment for effective development.
	</comments>
	<seeAlso>
	   <isbn>0201741172</isbn>
	   
	</seeAlso>

</book>


<book  scmsite="yes">
	<title>Continuous Integration: Improving Software Quality and Reducing Risk </title>
	<isbn>0321336380</isbn>
	<authors>Paul M Duvall</authors>
	<website>
		<url>http://www.integratebutton.com/</url>
		<description>Book Web Site</description>
	</website>
	<imageURL>cover/0321336380.jpg</imageURL>
	
	<categories>
		<category>ORGS-METHODS</category>
		<category>AGILE</category>
		<category>SYSTEMS</category>
		  <category>SCM</category>
	</categories>
	
	<comments>
This book is an excellent overview of why Continuous Integration is important and about more than just compiling frequently. The book helps you to understand why to do CI, what you can do beyond building, and how to do it. In addition to general principles, the book points you to some excellent tools and resources. This book is an excellent companion to Software Configuration Management Patterns; it provides teriffic information that support the build patterns in that book.
	</comments>
	<seeAlso>
	   <isbn>0201741172</isbn>
	   
	</seeAlso>

</book>
<!-- add Release It!-->
<book  scmsite="yes">
	<title>Release It! : Design and Deploy Production-Ready Software</title>
	<isbn>0978739213</isbn>
	<authors>Michael T Nygard</authors>
	<website>
		<url>http://www.pragmaticprogrammer.com/titles/prj/</url>
		<description>Book Web Site</description>
	</website>
	<imageURL>cover/0978739213.jpg</imageURL>
	
	<categories>
		<category>ORGS-METHODS</category>
		<category>AGILE</category>
	</categories>
	
	<comments>
This book helps you to understand why creating production ready code requires work at many levels: creating the deployment architecture, operations scenarios, and just plain writing code and testing. The book covers issues that every architect, developer and release engineer should know. The book has principles, patterns, and resources to help you identify production problems, prevent them, and survive them when all else fails.

One of the better features of the book is the stories that help you to understand issues and demonstrate that Nygard's lessons are based in experience. The lessons are (as the name of the series suggests) pragmatic, and each chapter leaves you with enough information to make changes to improve your application.

In books of this sort there is a balance between "principles" that are timeless and "how to" techniques that you can use immediately. This book is biased slightly towards Java, and contains a few references to current tools, there are enough  general principles that there is little in the book that will date it. 

As I read the book I found information about many topics that arose in each project that I have worked on, as well as things that I felt that I needed to learn more about. 

After I finished the book I felt energized to do things better. If you build enterprise applications buy this book to learn how to build more production-ready applications. If you already know the lessons in the book, buy a copy or two for your colleagues who may not so that your life will be easier and you can get fewer late-night phone calls about a system you helped build.
	</comments>
	<seeAlso>
	   <isbn>0201741172</isbn>
	   <isbn>0131479415</isbn>
	   <isbn>073561993X</isbn>
	   <isbn>020161622X</isbn>
	</seeAlso>

</book>

<book >
	<title>Ship it! A Practical Guide to Successful Software Projects</title>
	<isbn>0974514047</isbn>
	<authors>Jared Richardson and William Gwaltney</authors>
	<website>
		<url>http://www.pragmaticprogrammer.com/titles/prj/</url>
		<description>Book Web Site</description>
	</website>
	<imageURL>cover/0974514047.01._SCMZZZZZZZ_.jpg</imageURL>
	
	<categories>
		<category>ORGS-METHODS</category>
		<category>AGILE</category>
	</categories>
	
	<comments>If you need a good overview of what it takes to deliver software, give this book a look. It is easy to read, clearly written, and covers the important stuff. The book is geared at people who are less than experts, and as such covers some of the topics very briefly, but the book has some excellent pointers to other sources. The authors do a great job of collecting pointers to resources where you can learn more; you will want to keep the book around as a reference for them. The authors talk about a form of agile development that emphasizes tracer bullet development and a feature-based (as opposed to time boxed) approach to setting a delivery schedule. I tend to think that time boxed approaches are more useful, but the other good information in the book still makes sense if you use any approach to developing software. The authors also have some very practical advice on tool selection. The tools and infrastructure section of the book have pragmatic advice on how to implement the patterns in the Software Configuration Management Patterns book, and I wish that the authors had referenced the SCM Patterns book, if for no other reason than to help establish a common vocabulary in our domain. Over all, this is worth a read to learn (or reenforce) some of the basics about keeping a project running well.  And if you already know everything in the book, buy a copy for your colleagues who don't!

	</comments>
	<seeAlso>
	   <isbn>0201741172</isbn>
	   <isbn>0131479415</isbn>
	   <isbn>073561993X</isbn>
	   <isbn>020161622X</isbn>
	</seeAlso>

</book>
<book >
	<title>Collapse: How Societies Choose to Fail or Succeed</title>
	<isbn>0670033375</isbn>
	<authors>Jared Diamond</authors>
	<imageURL>cover/0670033375.01._SCMZZZZZZZ_.jpg</imageURL>
	
	<categories>

		<category>TECHSOC</category>

	</categories>
	<comments>
	 People and cultures seem to many things that don't make sense in retrospect. This book asks and attempts to answer the question of why once successful societies disappeared. Diamond combines an historical perspective with a discussion of modern day comunities so that we can see the parallels, and perhaps make better decisions in the future. While not an easy read, Diamond makes a complicated subject very approachable. This is a thought-provoking book that you should read if you are interested in society, the environment, or even just general decision making processes (if whole cultures can make decisions that cause them to fail, what can we expect from organizations!). 
	 </comments>
	<seeAlso>
		<isbn>0553803123</isbn>
		<isbn>0553585800</isbn>
		<isbn>0393317552</isbn>
		<isbn>0262112272</isbn>
	</seeAlso>
</book>
<book >
	<title>Forty Signs of Rain</title>
	<isbn>0553585800</isbn>
	<authors>Kim Stanley Robinson</authors>
	<imageURL>cover/0553585800.01._SCMZZZZZZZ_.jpg</imageURL>
	
	<categories>
		<category>FICTION</category>

	</categories>

	
	<comments>Robinson's books are imaginative stories which have their roots in fact and then explore what-if scenarios. Fourty Signs of Rain is part of a trilogy that explores the consequences of global warming. The story line has global implications, but the story is told from the perspective of a few characters who are leading somewhat ordinary lives in the midst of a changing world. The book combines fact, humor, and a lively style for a great read.

	</comments>
	<seeAlso>
		<isbn>0553803123</isbn>
		<isbn>0670033375</isbn>
	</seeAlso>
	</book>
	
	<book >
	<title>Fifty Degrees Below</title>
	<isbn>0553803123</isbn>
	<authors>Kim Stanley Robinson</authors>
	<imageURL>cover/0553803123.01._SCMZZZZZZZ_.jpg</imageURL>
	
	<categories>
		<category>FICTION</category>
	</categories>

	
	<comments>
 This is the second book in a trilogy that starts with Fourty Signs of Rain. This book is even more compelling and entertaining that the first book in the trilogy. Robinson again combines fact, humor, and real characters to entertain and educate.
	</comments>
	<seeAlso>
		<isbn>0553585800</isbn>
			<isbn>0670033375</isbn>
	</seeAlso>

</book>
<book>
	<title>Agile Estimating and Planning</title>
	<isbn>0131479415</isbn>
	<authors>Mike Cohn</authors>
	<imageURL>cover/0131479415.01._SCMZZZZZZZ_.jpg</imageURL>
	
	<categories>
		<category>ORGS-METHODS</category>
		<category>AGILE</category>
	</categories>

	
	<comments>This clearly written book provides insights into some common and vexing problems about how to do estimation and planning.  This book helps you to prioritize what you want to build as well as as how long it will take to build it.  The facts are complimented with stories from Mike Cohn's experience, which makes this book entertaining as well as informative. Much of the information in the book sounds obvious, but since few projects get estimation, scoping and planning right, it's pretty clear that it's only obvious in retospect. This book is a must have for people who are running agile teams and those who play the role of product owners. It will remain a useful reference througout the project. Even those on non-agile teams will find the chapters on selecting and prioritizing features useful.
</comments>
    <seeAlso>
      <isbn>0130676349</isbn>
      <isbn>0321278658</isbn>
      <isbn>073561993X</isbn>

    </seeAlso>
</book>


<book scmsite="yes">
	<title>Pragmatic Version Control Using Subversion</title>
	<isbn>0974514063</isbn>
	<authors>Mike Mason</authors>
	<imageURL>cover/0974514063.01._SCMZZZZZZZ_.jpg</imageURL>
	
	<categories>

		<category>SCM</category>

	</categories>

	
	<comments>Like the other Pragmatic Programmer books, this is an excellent resource for getting started using subversion

	</comments>
	<seeAlso>
	 <isbn>0974514004</isbn>
	   <isbn>0201741172</isbn>
	 </seeAlso>

</book>
<book>
<title>Testing Extreme Programming</title>
	<isbn>0321113551</isbn>
	<authors>Lisa Crispin and Tip House</authors>
	<imageURL>cover/0321113551.01._SCMZZZZZZZ_.jpg</imageURL>
	<categories>
 		<category>SYSTEMS</category>
			<category>AGILE</category>
			<category>ORGS-METHODS</category>
	</categories>
	<comments>This book explains, in detail, the value of having a tester role on an XP project. Much of what is written on XP focuses on the role of developers in writing tests, and this book will help you understand the value that testing professionals can add to an XP, or other agile, project. The function of a tester changes when a team applies XP; In the spirt  of lean software development, this book shows you how to apply the skills of testers in a new environment. One minor flaw in the book is that it is targeted at testers. While testers need to understand how to apply their skills to an XP environment, others such as Coaches, programmers and project managers also need to understand the value of testers. Get this book to understand how testers can improve your XP project.</comments>
<seeAlso>
<isbn>0321278658</isbn>
<isbn>0131177052</isbn>
  <isbn>1932394230</isbn>
</seeAlso>
</book>
<book >
	<title>Extreme Programming Explained : Embrace Change (2nd Edition)</title>
	<isbn>0321278658</isbn>
	<authors>Kent Beck and Cynthia Andres</authors>
	<imageURL>cover/0321278658.01._SCMZZZZZZZ_.jpg</imageURL>
    <categories>
      <category>ORGS-METHODS</category>
      <category>AGILE</category>
    </categories>
    <comments>This is an excellent book about how to develop software
    quickly in the face of changing requirements, and the definitive
    description of what Extreme Programming is.  The second edition
    reflects the experience of doing XP for the 5 years since the
    first edition came out. This edition clearly explains the
    relationships between principles, practices and values, which is a
    frequent topic of discussion in the XP community. Extreme
    Programming Explained, 2nd Edition is really about the human side
    of programming; With this book Kent Beck has earned a seat next to
    Jerry Weinberg as someone who understands how to apply an
    understanding of human nature to the problem of how to build
    software effectively. Get this book if you want to apply XP in
    your organization, or even if you simply want to improve your
    practices; there is much to learn from the XP approach, even if
    you can not, or will not, apply it fully.</comments>
<seeAlso>
      <isbn>0201741172</isbn>
      <isbn>020161622X</isbn>
      <isbn>0321146530</isbn>
      <isbn>0932633420</isbn>
      	<isbn>0131479415</isbn>
      	<isbn>0321205685</isbn>
    </seeAlso>

</book>


  <book  scmsite="yes">
    <title>Working Effectively with Legacy Code</title>
    <isbn>0131177052</isbn>
    <authors>Michael Feathers</authors>
    <imageURL>cover/0131177052.01._SCMZZZZZZZ_.jpg</imageURL>
    <categories>
      <category>SYSTEMS</category>
      <category>AGILE</category>
      <category>SW_PATTERNS</category>
    </categories>
    <comments>This book shows you how to apply patterns and
    refactorings to the task of untangling legacy code so that you can
    apply effective techniques like test driven development as you
    change the code. Since there will always be legacy code, this is a
    very practical book. The author emphasises the role of testing as
    a change enabler in a way that echos the the ideas in the SCM
    Patterns book.</comments>
    <seeAlso>
      <isbn>0201485672</isbn>
      <isbn>0321146530</isbn>
      <isbn>1932394230</isbn>
      <isbn>0201741172</isbn>
    </seeAlso>
  </book>


  <book  >
    <title>Fearless Change: Patterns for Introducing New Ideas</title>
    <isbn>0201741571</isbn>
    <authors>Mary Lynn Manns and Linda Rising</authors>
    <imageURL>cover/0201741571.01._SCMZZZZZZZ_.jpg</imageURL>
    <categories>
      <category>CREATE-SOLVE</category>
      <category>SW_PATTERNS</category>
      <category>TECHSOC</category>
      <category>ORGS-METHODS</category>
    </categories>
    <comments>
The material in this book is excellent, having been developed over a
number of years. In addition to wonderful, well written, patterns that
advise you on how to spread ideas, this books is full of stories that
help you to understand how to use the patterns effectively to influence people,
overcome roadblocks, and spread new ideas. Anyone who has new ideas to
share will benefit from this book including: Managers and Team
members, Professionals and Volunteers, people in industry and those in
community organizations.

</comments>
    <seeAlso>
      <isbn>0932633536</isbn>
      <isbn>0131467409</isbn>
    </seeAlso>
  </book>


  <book  >
    <title>Communication Gaps and How to Close Them</title>
    <isbn>0932633536</isbn>
    <authors>Naomi Karten</authors>
    <imageURL>cover/0932633536.01._SCMZZZZZZZ_.jpg</imageURL>
    <categories>
      <category>CREATE-SOLVE</category>
      <category>ORGS-METHODS</category>
        <category>PEOPLE</category>
    </categories>
    <comments>If you work with or live with other people you should read this book. It is filled with information on understanding how communication gaps happen, and practical advice for resolving commuunications issues with other people. Most of the advice seems obvious, yet it if often the obvious that one needs to be reminded of. Among the extremely practical bits of information in the book is are dicussions of communication models (so that you can understand why communication might break down), and a chapter on how to write Service Level Agreements.</comments>
    <seeAlso>
      <isbn>0201741571</isbn>
      <isbn>0131467409</isbn>
    </seeAlso>
  </book>

  <book scmsite="yes">
    <title>JUnit Recipes: Practical Methods for Programmer Testing</title>
    <isbn>1932394230</isbn>
    <authors>J. B. Rainsberger and Scott Stirling</authors>
    <imageURL>cover/1932394230.01._SCMZZZZZZZ_.jpg</imageURL>
    <categories>
      <category>SYSTEMS</category>
      <category>AGILE</category>
      <category>J2EE</category>
    </categories>

    <comments>Get this book both as an introduction to what JUnit
	can do for you and also as a reference when you are looking
	for information on how to solve a particular testing
	problem. The book covers the basics of using JUnit as well as issues around database and J2EE testing. It is filled with pointers to many frameworks and resources that can simplify your testing experience. This is not just a testing cookbook. J.B. also discusses issues such as how to design for testing (and how that can improve your architecture) as well as what to do when you need to test legacy code. This is an excellent guide to the details of how to use JUnit effectively. </comments>


    <seeAlso>
      <isbn>0321146530</isbn>
    </seeAlso>


  </book>


  <book>
    <title>Lean Thinking : Banish Waste and Create Wealth in Your Corporation, Revised and Updated</title>
    <isbn>0743249275</isbn>
    <authors>James P. Womack, Daniel T. Jones, James Womack and Daniel Jones</authors>
    <imageURL>cover/0743249275.01._SCMZZZZZZZ_.jpg</imageURL>
    <categories>
      <category>AGILE</category>
      <category>TECHSOC</category>
      <category>ORGS-METHODS</category>
    </categories>
    <comments>This book explains why lean manufacturing
works. There is much you can learn about lean software development by
learning about lean thinking in this, more concrete, domain. Read this
book to learn the more general concepts of lean production so that you
can better understand them and better explain them to your software
development colleagues and management.</comments>
    <seeAlso>
      <isbn>0321150783</isbn>
      <isbn>073561993X</isbn>

    </seeAlso>
  </book>




  <book>
    <title>Domain-Driven Design: Tackling Complexity in the Heart of Software</title>
    <isbn>0321125215</isbn>
    <authors>Eric Evans</authors>
    <imageURL>cover/0321125215.01._SCMZZZZZZZ_.jpg</imageURL>
    <categories>
      <category>SYSTEMS</category>
      <category>SW_PATTERNS</category>
    </categories>

    <comments>Developing a language to enable communication
	between team memembers and with domain experts seems like a
	common enough idea. Most teams do not do this and start their
	application by solving technology problems. This book
	describes the utility of a domain-driven approach to building
	systems and shows you how to apply this approach
	effectively. This book makes excellent use of patterns to
	demonstrate how design, architecture and development practices
	such as continuous integration interact with each other to
	determine how good your application will be. Like all good
	patterns books, the information in this book seems obvious
	once you read it. But it is material most people overlook. Buy
	this books to understand the value of a domain driven
	approach, or if you already understand that, use it as a guide
	for teaching others.</comments>

  </book>

  <book>
    <title>Organizational Patterns of Agile Software Development</title>
    <isbn>0131467409</isbn>
    <authors>James O. Coplien and Neil B. Harrison</authors>
    <imageURL>cover/0131467409.01._SCMZZZZZZZ_.jpg</imageURL>
    <categories>
      <category>AGILE</category>
      <category>SW_PATTERNS</category>
      <category>ORGS-METHODS</category>
    </categories>

    <comments>People build software systems in organizations, and
	the interesting problems often occur at the places where
	technology issues and people issues intersect.	An
	understanding of how software organizations work is
	essential to building good software systems.  Coplien and
	Harrison are two of the pioneers in writing patterns about software
	organizations, and this book is a useful guide to helping you
	understand how to build effective software development
	organizations. </comments>
    <seeAlso>
      <isbn>0932633536</isbn>
    </seeAlso>

  </book>

  <book>
    <title>Requirements by Collaboration: Workshops for Defining Needs</title>
    <isbn>0201786060</isbn>
    <authors>Ellen Gottesdiener</authors>
    <imageURL>cover/0201786060.01._SCMZZZZZZZ_.jpg</imageURL>
    <categories>
      <category>CREATE-SOLVE</category>
      <category>ORGS-METHODS</category>
    </categories>

    <comments>This book is about running requirements workshops and
more. Requirements workshops are an important tool for understanding
what you need to build. The techniques in this book will be useful in
many other group discussion settings, and will help you have more
productive meetings. The book discusses, among other things, roles in
workshops and decision rules (deciding how to decide). Each chapter
ends with a list of excellent references that you can use to probe
further on techniques. Anyone who is involved in group decision making
should own a copy of this book, read it, and refer back to it
often.</comments>

    <seeAlso>
      <isbn>0140157352</isbn>
      <isbn>0932633161</isbn>
      <isbn>020172183x</isbn>
    </seeAlso>

  </book>


  <book>
    <title>Agile Project Management with Scrum </title>
    <isbn>073561993X</isbn>
    <authors>Ken Schwaber</authors>
    <imageURL>cover/073561993X.01._SCMZZZZZZZ_.jpg</imageURL>
    <categories>
      <category>SYSTEMS</category>
      <category>AGILE</category>
      <category>ORGS-METHODS</category>
    </categories>
    <comments>
This book helped me understand more details about how to implement
Scrum. The combines some simple overviews of Scrum rules and practices
with case studies. The rules of Scrum are simple. Apply these rules in
your context can be tricky. I found that the case studies that thread
throughout the book really helped me to understand some of the nuances
of the Scrum process. And if you want a checklist, there is a appendix
that summarizes the rules of Scrum. This is a great book if you want to learn about Scrum as a project management tool, or if you have been trying to use Scrum and want a chance to renew your understanding.	  

</comments>
    <seeAlso>
      <isbn>0130676349</isbn>
      <isbn>0321278658</isbn>
      <isbn>0131479415</isbn>

    </seeAlso>
  </book>

  <book>
    <title>Pragmatic Project Automation: How to Build, Deploy, and Monitor Java Apps</title>
    <isbn>0974514039</isbn>
    <authors>Mike Clark</authors>
    <imageURL>cover/0974514039.01._SCMZZZZZZZ_.jpg</imageURL>
    <categories>
      <category>SYSTEMS</category>
      <category>AGILE</category>
      <category>SCM</category>
    </categories>
    <comments>Prag Auto is an excellent companion to the Scm patterns book if you are doing Java Dev.  It uses simple examples to show you how to set up a private workspace, integration build , release line among others. using open source tools. I wish that the book had referenced the patterns by name so as to set up a common vocabulary.</comments>
    <seeAlso>
      <isbn>0201741172</isbn>
    </seeAlso>
  </book>

  <book>
    <title>Pragmatic Version Control Using CVS</title>
    <isbn>0974514004</isbn>
    <authors>Dave Thomas and Andy Hunt</authors>
    <imageURL>cover/0974514004.01._SCMZZZZZZZ_.jpg</imageURL>
    <categories>
      <category>SYSTEMS</category>
      <category>AGILE</category>
      <category>SCM</category>
    </categories>
    <comments>Dave Thomas and Andy Hunt have written an excellent book, Pragmatic Version Control which explains how to use CVS in a basic and effective way. This book is an excellent companion to the SCM Patterns Book.</comments>

    <seeAlso>
      <isbn>0201741172</isbn>
      <isbn>0974514063</isbn>
    </seeAlso>

  </book>

  <book>
    <title>UML Distilled: A Brief  Guide to the Standard Object Modeling
Language, Third Edition</title>
    <isbn>0321193687</isbn>
    <authors>Martin Fowler</authors>
    <imageURL>cover/0321193687.01._SCMZZZZZZZ_.jpg</imageURL>
    <categories><category>SYSTEMS</category>
    <category>ORGS-METHODS</category>
    </categories>
    <comments>This is an excellent summary of the UML, and a great guide to how to
express OO models using the UML. If you buy only one UML book, get this one.
It The third edition is updated to the UML 2.0 spec. Fowler explains that
the book is best for people who want to sketch UML diagrams to explain their
designs, rather than who want to use UML for formally, but that may well be
all you need to do with UML. This book also explains some key concepts
of OO design. Every software developer should have a copy of
this book on their shelves! 
</comments></book>

  <book>
    <title>User Stories Applied : For Agile Software Development (Addison-Wesley Signature Series)</title>
    <isbn>0321205685</isbn>
    <authors>Mike  Cohn</authors>
    <imageURL>cover/0321205685.01._SCMZZZZZZZ_.jpg</imageURL>
    <categories>
      <category>SYSTEMS</category>
      <category>AGILE</category>
      <category>ORGS-METHODS</category>
    </categories>
    <comments>This is an excellent guide to writing User Stories. In addition to explaining what user stories are and how to write them, the book shows you how user stories fit into the development process and answers many of the common questions that arise when one starts writing stories. If you want to start using stories as part of your development process, buy this book; you'll want to read it and have it around for reference later.</comments>
  </book>





  <book>
    <title>JSTL in Action</title>
    <isbn>1930110529</isbn>
    <authors>Shawn Bayern</authors>
    <imageURL>cover/1930110529.01._SCMZZZZZZZ_.jpg</imageURL>
    <categories>
      <category>J2EE</category>
    </categories>
    <comments>This is a good book to learn about how to use JSTL. It has an excellent reference section, and the body of the book explains how to use the JSTL tags with many good example. On the whole, a very useful, readable book. One negative: The author has a sense of humor which some might find odd, and he interjects it throughout the book; at times it's distracting. But if you can get past that, you'll find this to be a good resource.</comments>

  </book> 
  <book>
    <title>Struts in Action: Building Web Applications with the
	Leading Java Framework</title> <isbn>1930110502</isbn>
    <authors>Ted Husted, Cedric Dumoulin, George Franciscus, David
	Winterfeldt and Craig R. McClanahan</authors>
    <imageURL>cover/1930110502.01._SCMZZZZZZZ_.jpg</imageURL>
    <categories>
      <category>SYSTEMS</category>
      <category>J2EE</category>
    </categories>
    <comments>I read this book after working on Struts
	applications for a few months, and it added understanding to
	my knowledge about Struts applications. I marked many pages
	that illustrated approaches that I wanted to use on my
	projects, either because my team had problems with that aspect
	of Struts, or because the approach in the book seemed
	better. In addition to explaining how to build Struts
	applications, it also provides good, practical, advice about
	structuring your Struts applications so that they are
	maintainable and understandable. I refer to this book often,
	and it is an excellent complement to the online
	documentation.</comments>
  </book>



  <book>
    <title>Design Patterns in C#</title>
    <isbn>0321126971</isbn>
    <authors>Steven John Metsker</authors>
    <imageURL>cover/0321126971.01._SCMZZZZZZZ_.jpg</imageURL>
    <categories>
      <category>SYSTEMS</category>
      <category>SW_PATTERNS</category>
    </categories>
    <comments>This book will serve you well whether you know
Patterns and are trying to learn C# or know C# and are trying to
understand Patterns better. It is not a replacement for the Design
Patterns Book or a good C+ reference, but it is an excellent companion
for both. </comments>
  </book>

  <book>
    <title>Software Configuration Management Implementation Roadmap</title>
    <isbn>0470862645</isbn>
    <authors>Mario E. Moreira</authors>
    <imageURL>cover/0470862645.01._SCMZZZZZZZ_.jpg</imageURL>
    <categories>
      <category>SYSTEMS</category>
      <category>SCM</category>
    </categories>
    <comments>Finding the path to the right process for your project
    and organization is tricky, and this book provides a map of the
    terrain that can guide you to the implementation appropriate for
    your project. This book will guide you through the steps that you
    need to take if you need to implement an SCM process for your
    organization at an organization, application, or project level.
    It includes customizable templates and examples to more quickly
    get you to your SCM goals.</comments>
    <seeAlso>
      <isbn>0201741172</isbn>
    </seeAlso>
  </book>

  <book>
    <title>Pair Programming Illuminated</title>
    <isbn>0201745763</isbn>
    <authors>Laurie Williams and Robert Kessler</authors>
    <imageURL>cover/0201745763.01._SCMZZZZZZZ_.jpg</imageURL>
    <categories>
      <category>AGILE</category>
      <category>ORGS-METHODS</category>
    </categories>
    <comments>This book answers many common questions about Pair Programming and supports the answers with data and stories. This is a very readable book, and will be an excellent resource for anyone trying to implement pair programming, or convince others of its usefulness in appropriate situations.</comments>
  </book>

  <book>
    <title>Joe Celko's SQL for Smarties: Advanced SQL Programming</title>
    <isbn>1558605762</isbn>
    <authors>Joe Celko</authors>
    <imageURL>cover/1558605762.01._SCMZZZZZZZ_.jpg</imageURL>
    <categories>
      <category>SYSTEMS</category>
    </categories>
    <comments>SQL for Smarties is a book that you should own if you work with relational databases.  It has good practical advice and good examples.  It is useful both for improving your SQL skills and as a reference.</comments>
  </book>


  <book>
    <title>Project Retrospectives: A Handbook for Team Reviews</title>
    <isbn>0932633447</isbn>
    <authors>Norm Kerth</authors>
    <imageURL>cover/0932633447.01._SCMZZZZZZZ_.jpg</imageURL>
    <categories>
      <category>ORGS-METHODS</category>
    </categories>
    <comments>Project Retrospectives is a must have for anyone who wants(or needs)to understand what happened on their last project. If you plan to conduct a retrospective, the book will show you how with exercises to use with your group.	Even if you do not run formal retrospectives, the techniques in this book will help you get a more candid view of how things on your project work.</comments>
  </book>


  <book>
    <title>Questioning Extreme Programming</title>
    <isbn>0201844575</isbn>
    <authors>Pete McBreen</authors>
    <imageURL>cover/0201844575.01._SCMZZZZZZZ_.jpg</imageURL>
    <categories>
      <category>SYSTEMS</category>
      <category>AGILE</category>
      <category>ORGS-METHODS</category>
    </categories>
    <comments>In this book McBreen gives a well reasoned
	discussion of what XP is and is not, when it works and when it
	might not work. The book is positive about the merits of XP,
	when used in the right setting. This book will be valuable to
	anyone who is considering changing their development approach,
	even is they are not considering Extreme Programming. Both
	enthusiast and skeptics alike will find the material in the
	book thought provoking.</comments>
    <seeAlso>
      <isbn>0321278658</isbn>
    </seeAlso>
  </book>

  <book>
    <title>Planning Extreme Programming</title>
    <isbn>0201710919</isbn>
    <authors>Kent Beck and Martin Fowler</authors>
    <imageURL>cover/0201710919.01._SCMZZZZZZZ_.jpg</imageURL>
    <categories>
      <category>SYSTEMS</category>
      <category>AGILE</category>
      <category>ORGS-METHODS</category>
    </categories>
    <comments>Planning Extreme Programming gives you advice on how
	to fit the XP Planning game, and related aspects into the
	larger context. This book will be particularly useful if you
	have had to reconcile the XP approach of incremental
	development and planning with an organization that takes a
	master plan approach.</comments>
  </book>
  <book>
    <title>Extreme Programming Installed</title>
    <isbn>0201708426</isbn>
    <authors>Ron Jeffries, Ann Anderson and Chet Hendrickson</authors>
    <imageURL>cover/0201708426.01._SCMZZZZZZZ_.jpg</imageURL>
    <categories>
      <category>SYSTEMS</category>
      <category>AGILE</category>
      <category>ORGS-METHODS</category>
    </categories>
    <comments>Extreme Programming Installed describes how to
	implement XP practices with practical advice based on
	experience. Buy this book when you are ready to implement XP
	for your team.</comments>
    <seeAlso>
      <isbn>0321278658</isbn>
    </seeAlso>
  </book>


  <book scmsite="yes">
    <title>Software Architecture: Organizational Principles and Patterns</title>
    <isbn>0130290327</isbn>
    <authors>David M. Dikel, David Kane and James R. Wilson</authors>
    <imageURL>cover/0130290327.01._SCMZZZZZZZ_.jpg</imageURL>
    <categories>
      <category>SYSTEMS</category>
      <category>SW_PATTERNS</category>
    </categories>
    <comments>This is one of the most useful books on software architecture that I have read. It discusses the qualities of a good architecture, and how the organization and process relates to the architecture.</comments>
  </book>
  <book>
    <title>Software Release Methodology</title>
    <isbn>0136365647</isbn>
    <authors>Michael E. Bays</authors>
    <imageURL>cover/0136365647.01._SCMZZZZZZZ_.jpg</imageURL>
    <categories>
      <category>SCM</category>
    </categories>
    <comments>This book has a good discussion of various types of codelines, as well as branching and merging strategies. It is clearly written and is a good resource if you want to go into more depth about branching strategies.</comments>
  </book>


  <book>
    <title>Artful Making: What Managers Need to Know About How Artists Work</title>
    <isbn>0130086959</isbn>
    <authors>Rob Austin and Lee Devin</authors>
    <imageURL>cover/0130086959.01._SCMZZZZZZZ_.jpg</imageURL>
    <categories>
      <category>SYSTEMS</category>
      <category>AGILE</category>
      <category>CREATE-SOLVE</category>
      <category>ORGS-METHODS</category>
    </categories>
    <comments>The principles that this book discusses: Release,
	Collaboration Ensemble and Play are extremely relevant to
	creating effective software teams. The principles are inspired
	by observing how theatre companies work, but they also have a
	basis in lean manufacturing.  If you work as a
	software developer or manager and have ever worked on a
	theatre production (community theatre or at school) a light
	will go on immediately. If you haven't The data that the
	authors provide about lean manufacturing practices and
	software development will convince you that there is a lot
	that we can learn from this metaphor. The theatre examples will be
	helpful in explaining how the principles work if you need to
	communicate them to a manager who does not understand software
	development. Buy this book and place it along side your books
	on agile software development; you will want to read it and refer
	back to it frequently.
</comments>
    <seeAlso>
      <isbn>0321150783</isbn>
    </seeAlso>

  </book>
  <book>
    <title>Test Driven Development: By Example</title>
    <isbn>0321146530</isbn>
    <authors>Kent Beck</authors>
    <imageURL>cover/0321146530.01._SCMZZZZZZZ_.jpg</imageURL>
    <categories>
      <category>SW_PATTERNS</category>
      <category>SYSTEMS</category>
      <category>AGILE</category>
    </categories>
    <comments>Through examples and a collection of patterns, this
	book explains what test driven development is, and what it is
	for. Every agile developer should read this book. 
</comments>
    <seeAlso>
      <isbn>0321278658</isbn>
    </seeAlso>
  </book>
  <book>
    <title>Lean Software Development: An Agile Toolkit for
	Software Development Managers</title> 
    <isbn>0321150783</isbn>
    <authors>Mary Poppendieck and Tom Poppendieck</authors>
    <imageURL>cover/0321150783.01._SCMZZZZZZZ_.jpg</imageURL>
    <categories> <category>SYSTEMS</category>
      <category>AGILE</category> </categories> 

    <comments>This is an
	excellent discussion of how the principles of Lean
	Manufacturing apply to Software Development. The authors
	explain why the usual metaphor of software as manufacturing is
	not quite right, and why the metaphor of Lean Manufacturing
	is. It is well written and will be useful to refer to as a
	reference.</comments> 
    <seeAlso>
      <isbn>0743249275</isbn>
    </seeAlso>
  </book>


  <book>
    <title>Mayhem: Violence As Public Entertainment</title>
    <isbn>0738201456</isbn>
    <authors>Sissela Bok</authors>
    <imageURL>cover/0738201456.01._SCMZZZZZZZ_.jpg</imageURL>
    <categories>
      <category>TECHSOC</category>
    </categories>
    <comments>Bok discusses the role of violence in popular culture. Aside from having a great title, this book is a very good discussion of the issues and how we can address them.</comments>
  </book>

  <book>
    <title>Flow</title>
    <isbn>0060920432</isbn>
    <authors>Mihaly Csikszentmihalyi</authors>
    <imageURL>cover/0060920432.01._SCMZZZZZZZ_.jpg</imageURL>
    <categories>
      <category>CREATE-SOLVE</category>
      <category>ORGS-METHODS</category>
    </categories>
    <comments>This book discusses the psychology of optimal
	experience, in other words, happiness. This books is
	not a how-to book, but rather a why book. Reading this book
	may give you great insights into how to enjoy all aspects of
	your work and private life.</comments>
  </book>


  <book>
    <title>Agile Software Development with SCRUM</title>
    <isbn>0130676349</isbn>
    <authors> Ken Schwaber and Mike Beedle</authors>
    <imageURL>cover/0130676349.01._SCMZZZZZZZ_.jpg</imageURL>
    <categories>
      <category>SYSTEMS</category>
      <category>ORGS-METHODS</category>
      <category>AGILE</category>
    </categories>
    <comments>Excellent book that explains Scrum, one of the more
	popular agile development techniques. The approach in this
	book is very pragmatic. The authors discuss what Scrum is and
	how to apply it in various environments.</comments>
    <seeAlso>
      <isbn>0201760436</isbn>
      <isbn>0321278658</isbn>
      <isbn>0932633609</isbn>
      <isbn>073561993X</isbn>
    </seeAlso>
  </book>


  <book>
    <title>Beyond Software Architecture: Creating and Sustaining Winning Solutions</title>
    <isbn>0201775948</isbn>
    <authors>Luke Hohmann</authors>
    <imageURL>cover/0201775948.01._SCMZZZZZZZ_.jpg</imageURL>
    <categories>
      <category>SYSTEMS</category>
      <category>SW_PATTERNS</category>
      <category>ORGS-METHODS</category>
    </categories>
    <comments>All you ever wanted to know about product
	management, but were afraid to ask. This book discusses the
	relationship between technical-architecture and
	marketing-architecture. This is an oft-neglected subject, but
	it is important as marketing and technology are both important
	for a successful product. This is a great book to read if you
	design software systems, or are involved in product
	management.</comments>
  </book>

  <book>
    <title>Waltzing With Bears: Managing Risk on Software Projects</title>
    <isbn>0932633609</isbn>
    <authors>Tom DeMarco and Timothy Lister</authors>
    <imageURL>cover/0932633609.01._SCMZZZZZZZ_.jpg</imageURL>
    <categories>
      <category>ORGS-METHODS</category>
      <category>AGILE</category>
    </categories>
    <comments>You should buy this book if you have any role in
	making decisions about your project. It discusses how how
	manage risks and explains why some corporate cultures
	discourage risk management, often to their disadvantage. The
	writing is very clear. This is a quick and informative
	read.</comments>
    <seeAlso>
      <isbn>0932633439</isbn>
      <isbn>0767907698</isbn>
    </seeAlso>
  </book>
  <book>
    <title>Configuration Management Principles and Practice</title>
    <isbn>0321117662</isbn>
    <authors>Anne Mette Jonassen Hass and Glenn Hass</authors>
    <imageURL>cover/0321117662.01._SCMZZZZZZZ_.jpg</imageURL>
    <categories>
      <category>SCM</category>
    </categories>
    <comments>This book is less about how to do SCM than about
	what SCM is. It is a great resource to read and to have on
	your shelf if you want to understand the scope of SCM. It is
	not entirely clear to me why this book is in AW's Agile
	series, but it is a worthwhile read so that you can understand
	what aspects of more formal SCM that you may be (justifiably)
	skipping on your project after you have implemented the
	techniques in the SCM Patterns book.</comments>

    <seeAlso>
      <isbn>0201741172</isbn>
    </seeAlso>
  </book>

  <book>
    <title>Peopleware : Productive Projects and Teams, 2nd Ed.</title>
    <isbn>0932633439</isbn>
    <authors>Tom Demarco and Timothy Lister</authors>
    <imageURL>cover/0932633439.01._SCMZZZZZZZ_.gif</imageURL>
    <categories>
      <category>SYSTEMS</category>
      <category>ORGS-METHODS</category>
    </categories>
    <comments>This is a classic book. Everyone involved with software systems: developers, managers, and customers, should read this book.</comments>
    <seeAlso>
      <isbn>0932633420</isbn>
      <isbn>0767907698</isbn>

    </seeAlso>
  </book>
  <book>
    <title>Writers' Workshops &amp; the Work of Making Things: Patterns, Poetry...</title>
    <isbn>020172183x</isbn>
    <authors>Richard Gabriel</authors>
    <imageURL>cover/020172183X.01._SCMZZZZZZZ_.jpg</imageURL>
    <categories>
      <category>SW_PATTERNS</category>
      <category>ORGS-METHODS</category>
      <category>CREATE-SOLVE</category>
    </categories>
    <comments>This is a unique book. It tells you about the
	writers workshop process. The writers workshop process has its
	origins in the creative writing community, and has been used
	in the software patterns community. Richard Gabriel explains
	how the process can also be used in other domains where
	creative effort is involved, such as reviewing marketing
	materials. I book for two reasons. First it provide great
	insight into the creative process (as applied to anything) and
	the values that are used in the writers workshop can benefit
	anyone who creates things, even if they don't use the workshop
	process. Second, if you do want to use writers workshops, this
	book explains the hows and whys of them. I had been involved
	in workshopping software patterns since 1995, and I though
	that I pretty much understood what they were about. I learned
	a lot reading this book.  I recommend this book for anyone who
	involved in the creative process(of any sort): Software
	engineers, writers, teachers, and students.</comments></book>


  <book>
    <title>Software Configuration Management Patterns: Effective  Teamwork, Practical Integration</title>
    <isbn>0201741172</isbn>
    <authors>Steve Berczuk (with Brad Appleton )</authors>
    <imageURL>cover/0201741172.01._SCMZZZZZZZ_.jpg</imageURL>
    <categories>
      <category>SW_PATTERNS</category>
      <category>SCM</category>
      <category>ORGS-METHODS</category>
    </categories>
    <comments>This book describes Essential SCM
practices. Developers,	team leaders and those just learning about
software  configuration management should find this book
useful.</comments>
    <infoURL>http://www.scmpatterns.com/</infoURL>
    <seeAlso>
      <isbn>0932633161</isbn>
      <isbn>020161622X</isbn>
      <isbn>1556159005</isbn>
      <isbn>0974514004</isbn>
      <isbn>0974514039</isbn>
    </seeAlso>

  </book>


  <book>
    <title>Patterns of Enterprise Application Architecture</title>
    <isbn>0321127420</isbn>
    <authors>Martin Fowler with David Rice, Matthew Foemmel, Edward Hieatt, Robert Mee and Randy Stafford</authors>
    <imageURL>cover/0321127420.01._SCMZZZZZZZ_.jpg</imageURL>
    <categories>
      <category>SYSTEMS</category>
      <category>J2EE</category>
      <category>SW_PATTERNS</category>
    </categories>
    <comments>This book is an excellent collection of tools to have
available when designing and building enterprise or web
applications. This is more of a patterns collection or pattern
catalog, than a pattern language, but the author ties the patterns
together in a way that makes it possible to compare and contrast the
various approaches. This is also a very readable book. Get a copy,
skim through it to get familiar with what is there, and keep it on
your shelf for ready reference.</comments>
    <infoURL>http://www.martinfowler.com/</infoURL>
  </book>

  <book>
    <title>Software Craftsmanship: The New Imperative</title>
    <isbn>0201733862</isbn>
    <authors>Pete  McBreen.</authors>
    <imageURL>cover/0201733862.01._SCMZZZZZZZ_.jpg</imageURL>
    <categories>
      <category>SYSTEMS</category>
    </categories>
    <comments>This book discusses the differences between a craft
approach and an engineering approach to building software,  and the
benefits of using a craft approach to build most  software
applications. It is a great book to read to learn  how to think about
your career, or how to build a software	 organization. This book is
not about Agile Development,   per se , but if you are interested in
that, you  should read this book too because the Agile development
works  best when there are people skilled in the craft of software
working on the project.</comments>
    <seeAlso>
      <isbn>0201741172</isbn>

    </seeAlso>
  </book>


  <book>
    <title>Slack: Getting Past Burnout, Busywork, and the Myth of Total	 Efficiency</title>
    <isbn>0767907698</isbn>
    <authors>Tom DeMarco.</authors>
    <imageURL>cover/0767907698.01._SCMZZZZZZZ_.jpg</imageURL>
    <categories>
      <category>ORGS-METHODS</category>
      <category>CREATE-SOLVE</category>
    </categories>
    <comments>This is an excellent book that explains very clearly how	working longer hours with fewer resources in the quest for  efficiency is counter productive for knowledge work, such as  software development. This is a quick read, with many	 interesting stories to support the assertions that the book  makes. The book is targeted at managers but also makes the  point that leadership can happen at any level in the	organization.</comments></book>


  <book>
    <title>Agile Software Development Ecosystems : Problems, Practices,	 and Principles</title>
    <isbn>0201760436</isbn>
    <authors>Jim Highsmith.</authors>
    <imageURL>cover/0201760436.01._SCMZZZZZZZ_.jpg</imageURL>
    <categories>
      <category>ORGS-METHODS</category>
      <category>AGILE</category>
    </categories>
    <comments>An excellent survey to the principles of agile
	development approaches such as	 Extreme  Programming , SCRUM,
	and others. The book mixes  discussions of the core ideas with
	interviews with some of	 the founders of the   Agile  Alliance
	.</comments>
    <seeAlso>
      <isbn>0130676349</isbn>
      <isbn>0321278658</isbn>
      <isbn>0201741172</isbn>
    </seeAlso>
  </book>


  


  <book>
    <title>Surviving Object-Oriented Projects. A Manager's Guide</title>
    <isbn>0201498340</isbn>
    <authors>Alistair Cockburn</authors>
    <imageURL></imageURL>
    <categories>
      <category>ORGS-METHODS</category>
      <category>SYSTEMS</category>
    </categories>
    <comments>A good overview of how a move to object technology can,  and cannot effect project success. Using case studies,  Alistair Cockburn describes the importance of people in the  success of an OO project. He also emphasises that the move to  object technology involves a different way of thinking, not	just a new programming language.</comments></book>


  <book>
    <title>The Deadline. A Novel About Project Management</title>
    <isbn>0932633390</isbn>
    <authors>Tom  DeMarco.</authors>
    <imageURL>cover/0932633390.01._SCMZZZZZZZ_.jpg</imageURL>
    <categories>
      <category>ORGS-METHODS</category>
    </categories>
    <comments>DeMarco's book is similar in style to	The Goal but covers software development rather than  manufacturing. The protagonist takes on a difficult  management assignment and learns many of th e lessons of  modern project management. It is a quick, enjoyable read, and  it passes on its lessons with humor, so they are easily  remembered. You will want to read some more traditional books  on project management, it addition to this book, but this  book motivates the lessons in more traditional books.</comments></book>


  <book>
    <title>The Psychology of Computer Programming, Silver Anniversary  Edition</title>
    <isbn>0932633420</isbn>
    <authors>Gerald M. Weinberg</authors>
    <imageURL>cover/0932633420.01._SCMZZZZZZZ_.jpg</imageURL>
    <categories>
      <category>ORGS-METHODS</category>
      <category>CREATE-SOLVE</category>
    </categories>
    <comments>A classic book! This is the original text with
	comments  by Weinberg at the end of each chapter on what he'd
	say  differently now. It is easy to get past the examples
	which  revolve around batch systems, and realize that the core
	ideas  in the book are still valid.</comments>
    <seeAlso>
      <isbn>0767907698</isbn>
    </seeAlso>
  </book>


  <book>
    <title>Becoming a Technical Leader : An Organic Problem-Solving  Approach</title>
    <isbn>0932633021</isbn>
    <authors>Gerald Weinberg.</authors>
    <imageURL>cover/0932633021.01._SCMZZZZZZZ_.jpg</imageURL>
    <categories>
      <category>ORGS-METHODS</category>
      <category>CREATE-SOLVE</category>
        <category>PEOPLE</category>
    </categories>
    <comments>This book has lots of good information for technical  people at all levels. This book even has some good work-style  and problem solving ideas for non-technical people.</comments>
    <seeAlso>
     <isbn>0932633013</isbn>
     <isbn>0932633528</isbn>
    </seeAlso>
    </book>


  <book>
    <title>The Secrets of Consulting</title>
    <isbn>0932633013</isbn>
    <authors>Gerald Weinberg.</authors>
    <imageURL>cover/0932633013.01._SCMZZZZZZZ_.jpg</imageURL>
    <categories>
      <category>ORGS-METHODS</category>
      <category>CREATE-SOLVE</category>
      <category>PEOPLE</category>
    </categories>
    <comments>Everyone consults, according to Weinberg, and you'll
find lots of useful stuff here, whether you are a full time  employee,
contract employee, or someone who is considering
consulting.</comments>
    <seeAlso><isbn>0932633528</isbn>
      <isbn>0932633161</isbn>
       <isbn>0932633021</isbn>
      
    </seeAlso>
  </book>


  <book>
    <title>More Secrets of Consulting: The Consultants Toolkit</title>
    <isbn>0932633528</isbn>
    <authors>Gerald Weinberg.</authors>
    <imageURL>cover/0932633528.01._SCMZZZZZZZ_.jpg</imageURL>
    <categories>
      <category>ORGS-METHODS</category>
      <category>CREATE-SOLVE</category>
        <category>PEOPLE</category>
    </categories>
    <comments>This book talks about how you can keep yourself
focused	 on doing the right things. The text and examples are geared
to consultants, but most everyone will find these "tools"
useful.</comments>
    <seeAlso><isbn>0932633013</isbn>
     <isbn>0932633021</isbn></seeAlso>
  </book>


  <book>
    <title>Systems Thinking</title>
    <isbn>0932633226</isbn>
    <authors>Gerald Weinberg</authors>
    <imageURL>cover/0932633226.01._SCMZZZZZZZ_.gif</imageURL>
    <categories>
      <category>ORGS-METHODS</category>
      <category>CREATE-SOLVE</category>
    </categories>
    <comments>The three books of the 4 volume Quality Software
	Management series I've read
	(Volume	 1:	Systems Thinking , Volume 2:	 First-Order
	Measurement , and Volume 3:	Congruent Action ) had really
	good stuff on the people  issues that affect software
	development. Even if you are not  a manager, these books
	provide you with information on how to	work more effectively
	with team members and managers alike,  and, understand, if not
	justify some annoying management  practices. (I haven't yet
	read Volume 4:	 Anticipating  Change , but there is probably
	valuable stuff in there as  well.)</comments></book>
  <book>
    <title>First-Order Measurement</title>
    <isbn>0932633242</isbn>
    <authors>Gerald Weinberg</authors>    
    <imageURL>cover/0932633242.01._SCMZZZZZZZ_.jpg</imageURL>
    <categories>
      <category>ORGS-METHODS</category>
      <category>CREATE-SOLVE</category>
    </categories>
    <comments>Even if you are not  a manager, the books in this
	Quality Software Management Series provide you with
	information on how to  work more effectively with team members
	and managers alike,  and, understand, if not justify some
	annoying management  practices. </comments></book>

  <book><title>Congruent Action</title>
    <isbn>0932633285</isbn>
    <authors>Gerald Weinberg</authors>
    <imageURL>cover/0932633285.01._SCMZZZZZZZ_.jpg</imageURL>
    <categories>
      <category>ORGS-METHODS</category>
      <category>CREATE-SOLVE</category>
    </categories>
    <comments>Even if you are not  a manager, the books in this
	Quality Software Management Series provide you with information on how to  work more effectively with team members and managers alike,	and, understand, if not justify some annoying management  practices. </comments></book>


  <book>
    <title>Sources of Power. How People Make Decisions</title>
    <isbn>0262112272</isbn>
    <authors>Gary  Klein.</authors>
    <imageURL>cover/0262112272.01._SCMZZZZZZZ_.jpg</imageURL>
    <categories><category>ORGS-METHODS</category></categories>
    <comments>This book is about how people make decisions in a variety	 of circumstances. This includes solo decision making in  crisis situations, as well as team decisions. Discusses the  value of stories in expressing and clarifying the decision  making process. The discussion of stories (known uses) and  the importance of clarifying intent while giving instructions  make this worthwhile reading for those studying patterns as a  means of conveying expertise.</comments></book>


  <book>
    <title>Journey of the Software Professional: A Sociology of Software  Development</title>
    <isbn>0132366134</isbn>
    <authors>Luke Hohmann</authors>
    <imageURL>cover/0132366134.01._SCMZZZZZZZ_.jpg</imageURL>
    <categories>
      <category>ORGS-METHODS</category>
      <category>CREATE-SOLVE</category>
       <category>PEOPLE</category>
    </categories>
    <comments>This book really made me think about my work, both day to	 day and career-wise. Covers practical approaches to improving	culture, communication, and work environment. My favorite  chapters were   Avoiding Bad Working Environments and   Working In a Poor Environment .</comments></book>


  <book>
    <title>How Good People Make Tough Choices: Resolving the Dilemmas of  Ethical Living</title>
    <isbn>0684818388</isbn>
    <authors>Rushworth M. Kidder.</authors>
    <imageURL>cover/0684818388.01._SCMZZZZZZZ_.jpg</imageURL>
    <categories>
      <category>CREATE-SOLVE</category>
    </categories>
    <comments>This book describes a framework for analyzing and
resolving ethical dilemmas. It does not provide you with  answers, but
it does provide a great way of thinking about  the issues and how to
resolve them. The text has examples  based on real situations: from
life-and-death scenarios, to  the more banal, but still
difficult.</comments>

    <seeAlso>
      <isbn>0932633161</isbn>
    </seeAlso></book>


  <book>
    <title>Difficult Conversations : How to Discuss What Matters  Most</title>
    <isbn>014028852X</isbn>
    <authors>Douglas Stone, Bruce Patton and Sheila Heen.</authors>
    <imageURL>cover/014028852X.01._SCMZZZZZZZ_.jpg</imageURL>
    <categories>
      <category>CREATE-SOLVE</category>
      <category>ORGS-METHODS</category>
        <category>PEOPLE</category>
    </categories>
    <comments>An excellent resource on how to approach issues at work  and at home. Should be required reading for everyone who is  part of a team or a relationship.</comments>
     <seeAlso>
      <isbn>0140157352</isbn>
      <isbn>0553371312</isbn>

    </seeAlso>
    </book>


  <book>
    <title>Getting to Yes : Negotiating Agreement Without Giving In</title>
    <isbn>0140157352</isbn>
    <authors>Roger Fisher and William Ury.</authors>
    <imageURL>cover/0140157352.01._SCMZZZZZZZ_.jpg</imageURL>
    <categories><category>CREATE-SOLVE</category>
      <category>PEOPLE</category>
    </categories>
    <comments>This is one of the &quot;classic&quot; books on
	negotiation, and  still worth a read. This book is worth
	reading if you need to	negotiate <em>anything </em>
	(requirements, assignments,  schedules) as part of your
	job. It also has some insights	that will help in personal
	relationships.</comments>
    <seeAlso>
      <isbn>014028852X</isbn>
      <isbn>0553371312</isbn>

    </seeAlso>
  </book>



  <book>
    <title>Getting Past No : Negotiating Your Way from Confrontation to	 Cooperation</title>
    <isbn>0553371312</isbn>
    <authors>William Ury.</authors>
    <imageURL>cover/0553371312.01._SCMZZZZZZZ_.jpg</imageURL>
    <categories><category>CREATE-SOLVE</category>
      <category>PEOPLE</category>
      </categories>
    <comments>This book builds on     Getting to Yes . If you find yourself in having trouble  making headway in negitiation situations, it is worth a read.  But read	   Getting to Yes first.</comments>
    <seeAlso>
     <isbn>0140157352</isbn>
      <isbn>014028852X</isbn>
    </seeAlso>
    </book>


  <book>
    <title>Are Your Lights On?</title>
    <isbn>0932633161</isbn>
    <authors>Gerald M. Weinberg.</authors>
    <imageURL>cover/0932633161.01._SCMZZZZZZZ_.jpg</imageURL>
    <categories>
      <category>CREATE-SOLVE</category>
        <category>PEOPLE</category>
    </categories>
    <comments>An easy to read, entertaining book that illustrates  quite clearly what some people never really learn: you need	to know what the problem is before looking for a  solution.</comments></book>


  <book>
    <title>Analysis Patterns</title>
    <isbn>0201895420</isbn>
    <authors>Martin Fowler.</authors>
    <imageURL>cover/0201895420.01._SCMZZZZZZZ_.jpg</imageURL>
    <categories>
      <category>SYSTEMS</category>
      <category>SW_PATTERNS</category>
    </categories>
    <comments>Patterns on how to model business and systems and	 organizations. This book will save you from heading into a  lot of dead ends if you walk into a system when you need to  model a business process.   A book which covers similar material, but from a database	 modeling point of view is     Data Model Patterns by David Hay. While these are  "patterns" in the more conventional sense (recurring	structures, but not broken down into  Problem/Context/Solution), this book will tell you a lot	about database design.</comments></book>


  <book>
    <title>Design Patterns</title>
    <isbn>0201633612</isbn>
    <authors>the "Gang of Four" (Gamma, Helm,  Johnson &amp; Vlissides).</authors>
    <imageURL>cover/0201633612.01._SCMZZZZZZZ_.jpg</imageURL>
    <categories>
      <category>SW_PATTERNS</category>
      <category>SYSTEMS</category>
    </categories>
    <comments>This the one book everyone who talks about patterns has  should read. It collects the basic software design idioms  everyone doing object-oriented software development should  know.</comments></book>


  <book>
    <title>Pattern Hatching</title>
    <isbn>0201432935</isbn>
    <authors>the John Vlissides .</authors>
    <imageURL>cover/0201432935.01._SCMZZZZZZZ_.jpg</imageURL>
    <categories>
      <category>SW_PATTERNS</category>
      <category>SYSTEMS</category>
    </categories>
    <comments>Using   Design Patterns in more detail. This book discusses  some of the fine points of the Patterns in	  Design Patterns . This is a well written book that is	 based on a series of columns from   C++ Report . Unlike many compilations of columns,	this book reads like a coherent book.</comments></book>


  <book>
    <title>A System of Patterns</title>
    <isbn>0471958697</isbn>
    <authors>Buschmann, Meunier, Rohnert,  Sommerlad, Stal.</authors>
    <imageURL>cover/0471958697.01._SCMZZZZZZZ_.jpg</imageURL>
    <categories>
      <category>SW_PATTERNS</category>
      <category>SYSTEMS</category>
    </categories>
    <comments>This book has system level patterns than design patterns.	 It also uses a lot of examples from distributed systems.</comments></book>


  <book>
    <title>A Pattern Language</title>
    <isbn>0195019199</isbn>
    <authors>Christopher Alexander, Sara  Ishikawa, Murray Silverstein</authors>
    <imageURL>cover/0195019199.01._SCMZZZZZZZ_.jpg</imageURL>
    <categories>
      <category>ARCH_PATTERNS</category>
    </categories>
    <comments>A must read if you are interested in patterns or	architecture or urban planning. In the software patterns  community,   A Pattern Language is often used as an example of  how, a pattern language (as opposed to solitary patterns)  should be structured.</comments></book>


  <book>
    <title>The Timeless Way of Building</title>
    <isbn>0195024028</isbn>
    <authors>Christopher  Alexander</authors>
    <imageURL>cover/0195024028.01._SCMZZZZZZZ_.jpg</imageURL>
    <categories><category>ARCH_PATTERNS</category></categories>
    <comments>The philiosphy behind patterns and pattern languages.  Really helpful in understanding the   why of patterns.</comments></book>


  <book>
    <title>The Oregon Experiment</title>
    <isbn>0195018249</isbn>
    <authors>Christopher Alexander</authors>
    <imageURL>cover/0195018249.01._SCMZZZZZZZ_.jpg</imageURL>
    <categories><category>ARCH_PATTERNS</category></categories>
    <comments>This book gives a concrete example of how one would  apply patterns and pattern languages to a  planning/architecture project. Talks about a project at the  University of Oregon. Reading this book put some key ideas  into focus, like how you use patterns when not starting from  scratch, and how to deal with specialized situations where	 the book of patterns you have doesn't cover everything.</comments></book>


  <book>
    <title>The Pragmatic Programmer: From Journeyman to Master</title>
    <isbn>020161622X</isbn>
    <authors></authors>
    <imageURL>cover/020161622X.01._SCMZZZZZZZ_.jpg</imageURL>
    <categories>
      <category>SYSTEMS</category>
    </categories>
    <comments>This is an excellent book that explains very clearly
many  practical things that people often ignore. A great book to
read, and one that you will want to re-read sections of from  time to
time.</comments>

    <seeAlso>
      <isbn>0201741172</isbn>
    </seeAlso>
  </book>


  <book>
    <title>Refactoring: Improving the Design of	 Existing Code</title>
    <isbn>0201485672</isbn>
    <authors>Martin Fowler</authors>
    <imageURL>cover/0201485672.01._SCMZZZZZZZ_.jpg</imageURL>
    <categories>
      <category>SYSTEMS</category>
      <category>SW_PATTERNS</category>
    </categories>
    <comments>This book describes what to do to change code that has   gotten messy with time, and how to proceeed to make the	changes. If you've been doing Object-Oriented programming for  a while you probably know much of what is in here, but it is  worth reading anyway, both as a reminder, and as a way to	explain the techniques to others. Fowler describes the	refactorings very clearly, with guidelines on when to use  each technique. Like Design Patterns, this book provides a  vocabulary for the important techniques you use to change  code. The examples are in Java, but the techniques can be  adapted to any OO language, such as C++ quite readily.</comments></book>


  <book>
    <title>Software for Use: A Practical Guide to the Models and Methods  of Usage-Centered Design</title>
    <isbn>0201924781</isbn>
    <authors>By Larry L. Constantine and Lucy  A. D. Lockwood</authors>
    <imageURL>cover/0201924781.01._SCMZZZZZZZ_.jpg</imageURL>
    <categories>
      <category>SYSTEMS</category>
      <category>ORGS-METHODS</category>
    </categories>
    <comments>This is an excellent book about how to build good	 interfaces. The book, at first glance, is geared towards  uasbility professionals, but anyone who has a role in  building or specifying systems that have some sort of user  interface will benefit from reading, and referring to, this  book.</comments></book>


  <book>
    <title>Rapid Development, Taming Wild Software  Schedules</title>
    <isbn>1556159005</isbn>
    <authors>Steve McConnell.</authors>
    <imageURL>cover/1556159005.01._SCMZZZZZZZ_.jpg</imageURL>
    <categories>
      <category>ORGS-METHODS</category>
      <category>SYSTEMS</category>
    </categories>
    <comments>An excellent book that describes best practices for
the  entire software development lifecycle. This should be  required
reading for anyone planning or working on a software
project.</comments>
    <seeAlso>
      <isbn>0201741172</isbn>

    </seeAlso>
  </book>


  <book>
    <title>Component Software: Beyond Object-Oriented  Programming</title>
    <isbn>0201178885</isbn>
    <authors>Clements Szyperski.</authors>
    <imageURL></imageURL>
    <categories>
      <category>SYSTEMS</category>
    </categories>
    <comments>This is an excellent discussion about component software.	 It covers general issues involved in component design and  distribution, including technical issues and marketing  issues. It provides a good comparison of the major component  technologies (COM, CORBA and Java Beans), and it also	 contains a good deal of timeless information. While this is  not always light reading, it is very well written. This is a  book developers, architects, and product managers can all  read parts of!</comments></book>


  <book>
    <title>HTTP: The Definitive Guide</title>
    <isbn>1565925092</isbn>
    <authors>David Gourley</authors>
    <imageURL>cover/1565925092.01._SCMZZZZZZZ_.jpg</imageURL>
    <categories><category>SYSTEMS</category></categories>
    <comments>This book does a great job of describing enough of what  you need to know about HTTP to have a useful conversation  about web architecture. It is written well enough that you  can just read through it, and it also make a great resource  when you need to look something up. And there is all sorts of  useful reference material in the appendicies.</comments></book>


  <book>
    <title>Designing Web Usability</title>
    <isbn>156205810X</isbn>
    <authors>Jakob Nielson</authors>
    <imageURL>cover/156205810X.01._SCMZZZZZZZ_.jpg</imageURL>
    <categories>
      <category>SYSTEMS</category>
    </categories>
    <comments>An excellent book. It describes what is in an effective  web sites, and provides many examples of good and bad web  design. People who work with web sites at all levels: users,	project managers, and people who implement web sites, will  find this book incredibly useful and inspirational. Read this  book before doing any work on a web site or intranet.</comments></book>


  <book>
    <title>The XML Companion(3rd Edition)</title>
    <isbn>0201770598</isbn>
    <authors>Neil Bradley</authors>
    <imageURL>cover/0201770598.01._SCMZZZZZZZ_.jpg</imageURL>
    <categories>
      <category>SYSTEMS</category>
    </categories>
    <comments>The best guide and refererence to XML I've seen so far.  I've had people recommend     The XML Bible by Harold to me, but this book seems like a	more useful reference.</comments></book>


  <book>
    <title>The XSL Companion (2nd Edition)</title>
    <isbn>0201770830</isbn>
    <authors>Neil Bradley</authors>
    <imageURL>cover/0201770830.01._SCMZZZZZZZ_.jpg</imageURL>
    <categories>
      <category>SYSTEMS</category>
    </categories>
    <comments>Like his book on XML, this book gives you enough to get started, and has enough in it to keep as a refererence.</comments>
  </book>

  <book>
    <title>How Buildings Learn : What Happens After They're Built</title>
    <isbn>0140139966</isbn>
    <authors>Stewart Brand.</authors>
    <imageURL>cover/0140139966.01._SCMZZZZZZZ_.jpg</imageURL>
    <categories>
      <category>TECHSOC</category>
      <category>ARCH_PATTERNS</category>
    </categories>
    <comments>This is a great book if you are interested in  architecture, history, or just simply how systems change and  grow over time.</comments></book>


  <book>
    <title>The Clock of the Long Now : Time and Responsibility</title>
    <isbn>0465007805</isbn>
    <authors>Stewart Brand</authors>
    <imageURL>cover/0465007805.01._SCMZZZZZZZ_.jpg</imageURL>
    <categories><category>TECHSOC</category></categories>
    <comments>An interesting book. Brand discusses the	 Long Now project, but	puts it in the context of the different time scales we all  work on. If you didn't already understand it, this book  explains when and why the long view is necessary. I think	that this is a worthwhile read for systems designers, as well  as excellent general interest reading.</comments></book>


  <book>
    <title>Guns, germs, and steel : the fates of human societies</title>
    <isbn>0393317552</isbn>
    <authors>Jared M. Diamond</authors>
    <imageURL>cover/0393317552.01._SCMZZZZZZZ_.jpg</imageURL>
    <categories><category>TECHSOC</category></categories>
    <comments>Interesting, and well written, historical overview of  how the environment shaped the development of human society.  It's a sort of history of the world in 400 pages. This book	gives lots of examples of the differences between apparent  causes and root causes. It you like history, or are often  curious about why things are, this is a worthwhile book.</comments></book>


  <book>
    <title>The Victorian Internet</title>
    <isbn>0802713424</isbn>
    <authors>Tom Standage</authors>
    <imageURL>cover/0802713424.01._SCMZZZZZZZ_.jpg</imageURL>
    <categories><category>TECHSOC</category></categories>
    <comments>This book describes parallels between the social impact  of the telegraph and that of the Internet. The title put me  off the book initially, since I thought that comparisions  between the telegraph and the Internet would be tenuous.	 Howev er, I was surprised to find out that there were issues  about on-line romances, on-line fraud, among other familiar  sounding issues, in the age of the telegraph. This book is	yet another reminder that there are a whole host of issues  that continue to arise whenever a new communications  technology is introduced. A quick, interesting read.</comments></book>


  <book>
    <title>How the Mind Works</title>
    <isbn>0393318486</isbn>
    <authors>Steve Pinker.</authors>
    <imageURL>cover/0393318486.01._SCMZZZZZZZ_.gif</imageURL>
    <categories><category>TECHSOC</category></categories>
    <comments>The title pretty much explains it. Given the title this  is a very approachable book, and even has its amusing  moments. I found it a bit easier to read than	The Language Instinct , which is also worth a look if you  are interested in where language comes from.</comments></book>


  <book>
    <title>The Invisible Computer</title>
    <isbn>0262140659</isbn>
    <authors>Donald A. Norman.</authors>
    <imageURL>cover/0262140659.01._SCMZZZZZZZ_.jpg</imageURL>
    <categories>
      <category>TECHSOC</category>
      <category>SYSTEMS</category>
    </categories>
    <comments>A mix of Norman's usual excellent ideas about usability  combined with the market concepts of	Crossing The Chasm . An excellent book that guides us to  the coming era when computers are in tools we use everyday,  rather than complicated devices we need to be experts to	 use.</comments></book>


  <book>
    <title>The Practice of Programming</title>
    <isbn>020161586X</isbn>
    <authors>B. W. Kernighan and R.  Pike</authors>
    <imageURL></imageURL>
    <categories>
      <category>SYSTEMS</category>
    </categories>
    <comments>A collection of good, time tested, ideas. The authors  give examples in C++, Java, scripting languages, and C. The  examples are biased towards C, but there are good general  principles about design, coding, debugging and testing.  Combine this book with   Multi-Paradigm Design  for C++ , and you will have inspiration to look at  problems multiple ways before jumping in and coding.</comments></book>


  <book>
    <title>Programming Pearls</title>
    <isbn>0201657880</isbn>
    <authors>Jon Louis Bentley</authors>
    <imageURL>cover/0201657880.01._SCMZZZZZZZ_.jpg</imageURL>
    <categories>
      <category>SYSTEMS</category>
    </categories>
    <comments>This is one of those classic books that you should read.	Lots of good programming basics.</comments></book>


  <book>
    <title>Code Complete</title>
    <isbn>1556154844</isbn>
    <authors>Steve McConnell.</authors>
    <imageURL></imageURL>
    <categories>
      <category>SYSTEMS</category>
    </categories>
    <comments>This book is an excellent resource about the mechanics of	 coding. While some of the examples are language specific, the	principles are general. You should at least skim through, if  not read and own, this book at some point in your	 career.</comments></book>


  <book>
    <title>Multi-Paradigm Design for C++</title>
    <isbn>0201824671</isbn>
    <authors>Jim  Coplien.</authors>
    <imageURL>cover/0201824671.01._SCMZZZZZZZ_.jpg</imageURL>
    <categories><category>SYSTEMS</category></categories>
    <comments>Coplien explains how to apply   commonality and variability analysis to solve  problems using   all the tools at the disposal of the C++ programmer.  The book shows how and when to combine the object-oriented,	 functional, and generic paradigms along with other tools such	as patterns. The book is primarily of use to the experienced  C++ developer/designer, but anyone with a interest in how	 software design is influenced by the application language  will find the book interesting.</comments></book>


  <book>
    <title>C++ Primer</title>
    <isbn>0201824701</isbn>
    <authors>Stanley Lippman and Josee Lajoie.</authors>
    <imageURL>cover/0201824701.01._SCMZZZZZZZ_.jpg</imageURL>
    <categories><category>SYSTEMS</category></categories>
    <comments>This is an excellent book to introduce someone to C++  with. I've recommended the previous editions to people, with  much success. The third edition is updated for the standard,	 and includes information on the standard library, STL, etc.  This book is much more approachable to Stroustrup's     The C++ Programming Language 2nd Edition . I'd buy this  book first, and then the	    The C++ Programming Language . They both should be part of	a C++ developer's library.</comments></book>


  <book>
    <title>Effective C++ Second Edition</title>
    <isbn>0201924889</isbn>
    <authors>Scott Meyers.</authors>
    <imageURL>cover/020163371X.01._SCMZZZZZZZ_.jpg</imageURL>
    <categories><category>SYSTEMS</category></categories>
    <comments>This book and	More Effective C++ list many of the idioms a serious C++  programer should know.</comments></book>


  <book>
    <title>The Design and Evolution of C++</title>
    <isbn>0201543303</isbn>
    <authors>Bjarne  Stroustrup.</authors>
    <imageURL></imageURL>
    <categories><category>SYSTEMS</category></categories>
    <comments>This book discusses some of the history of C++. It will  help you understand why some of the parts of the C++ Language  that seem broken are in the language. (Hint: most have to do  with compatability with C.)</comments></book>



<!--

  <book>
    <title>The Unified Modeling Language User  Guide</title>
    <isbn>0201571684</isbn>
    <authors>Grady Booch, Jim Rumbaugh and Ivar	 Jacobson</authors>
    <imageURL></imageURL>
    <categories><category>UML</category></categories>
    <comments>An excellent book to have on your bookshelf if you work  with UML. Provides a good overview of the UML.</comments></book>


  <book>
    <title>The Unified Modeling Language Reference  Manual</title>
    <isbn>020130998X</isbn>
    <authors>James Rumbaugh, Ivar Jacobson and Grady  Booch</authors>
    <imageURL></imageURL>
    <categories><category>UML</category></categories>
    <comments>Some good material at the beginning. The rest is	reference, which may not be terribly useful, but you never  know. Good book to have on your shelf.</comments></book>


  <book>
    <title>Developing Software with UML</title>
    <isbn>0201398265</isbn>
    <authors>Bernd  Oestereich</authors>
    <imageURL></imageURL>
    <categories><category>UML</category></categories>
    <comments>This book is not a "must have" if you own any of the  Three Amigos books. What this book adds is a summary of the	 Object Constraint Language, and some examples of how to use  UML in the context of a project. Buy it if you have some	extra money and are seeking UML examples.</comments></book>
-->

  <book>
    <title>Pattern Languages of Programs Design 1</title>
    <isbn>0201607344</isbn> <authors>Edited by Coplien &amp;
	Schmidt</authors> <imageURL></imageURL>
    <categories><category>SW_PATTERNS</category></categories>
    <comments>Volume 1 of the PLoPD series, A compilation of the
	"Best of" the PLoP and EuroPLoP conferences. Not as handy for
	reference material as some of the other patterns books, but
	good to have on your shelf because people in the patterns
	community will often reference the patterns here (and some may
	very well address your problem):</comments></book>

  <book>
    <title>Pattern Languages of Programs Design 2</title>
    <isbn>0201895277</isbn> 

    <authors>Edited by Vlissides, Colpien &amp; Kerth</authors> <imageURL></imageURL>
    <categories><category>SW_PATTERNS</category></categories>
    <comments>Volume 2 of the PLoPD series, A compilation of the
	"Best of" the PLoP and EuroPLoP conferences. Not as handy for
	reference material as some of the other patterns books, but
	good to have on your shelf because people in the patterns
	community will often reference the patterns here (and some may
	very well address your problem):</comments></book>

  <book>
    <title>Pattern Languages of Programs Design 3</title>
    <isbn>0201310112</isbn> 
    <authors>Edited by Martin, Riehle &amp; Buschmann</authors> 
    <imageURL></imageURL>
    <categories><category>SW_PATTERNS</category></categories>
    <comments>Volume 3 of the PLoPD series, A compilation of the
	"Best of" the PLoP and EuroPLoP conferences. Not as handy for
	reference material as some of the other patterns books, but
	good to have on your shelf because people in the patterns
	community will often reference the patterns here (and some may
	very well address your problem):</comments></book>

  <book>
    <title>Pattern Languages of Programs Design 3</title>
    <isbn>0201398265</isbn> 
    <authors>Edited by Neil Harrison, Brian Foote &amp; Hans Rohner</authors> 
    <imageURL></imageURL>
    <categories><category>SW_PATTERNS</category></categories>
    <comments>Volume 4 of the PLoPD series, A compilation of the
	"Best of" the PLoP and EuroPLoP conferences. Not as handy for
	reference material as some of the other patterns books, but
	good to have on your shelf because people in the patterns
	community will often reference the patterns here (and some may
	very well address your problem):</comments></book>


  <book>
    <title>Emergence: The Connected Lives of Ants, Brains, Cities, and Software</title>
    <isbn>068486875X</isbn>
    <authors>Steven Johnson</authors>
    <imageURL>cover/068486875X.01._SCMZZZZZZZ_.jpg</imageURL>
    <categories>
      <category>TECHSOC</category>
    </categories>
    <comments>An interesting book that talks about  self-organizing (or emergent) systems. This book gives you lots to think about, especially about the power of independent agents acting bottom-up can have.</comments>
  </book>

  <book>
    <title>The Pattern on the Stone : The Simple Ideas That Make Computers Work (Science Masters Series)</title>
    <isbn>046502596x</isbn>
    <authors>Daniel Hillis and W. Daniel Hillis</authors>
    <imageURL>cover/046502596X.01._SCMZZZZZZZ_.jpg</imageURL>
    <categories>
      <category>TECHSOC</category>
    </categories>

    <comments>This is a very good to the basic ideas behind how
	computers work. Hillis intrpoduces concepts such as boolean
	algebra, algorithms, finite state machines, turing machines,
	and even emergent behavior. I recommend this book if you
	already understand the ideas, but what to explain them to
	someone, or for the somewhat mathematically inclined person
	who wants to understand how computers work. You don't need to
	be a math maven to understand this book, but an inclination
	towards logical thinging helps.</comments>
  </book>







</books>

