Author Description

To start a discussion about software architecture, we have to define what architecture is. I love Martin Fowler's definition of a myriad of subtly contradictory meanings. One of the biggest sufferers is "architecture". I see "architecture" as of those impressive-sounding words, used mostly to indicate that we are talking about something important. However, I'm pragmatic enough not to let my cynicism get in the way of the challenge of getting people to my book."he Pragmatic Programmer cuts through the increasing specialization and technicalities of modern software development to examine the core process--taking a requirement and producing working, maintainable code that delights its users. It covers topics ranging from personal responsibility and career development to architectural techniques for keeping your code flexible and easy to adapt and reuse. Read this book, and youll learn how to *Fight software rot; *Avoid the trap of duplicating knowledge; *Write flexible, dynamic, and adaptable code; *Avoid programming by coincidence; *Bullet-proof your code with contracts, assertions, and exceptions; *Capture real requirements; *Test ruthlessly and effectively; *Delight your users; *Build teams of pragmatic programmers; and *Make your developments more precise with automation. Written as a series of self-contained sections and filled with entertaining anecdotes, thoughtful examples, and interesting analogies