+1 to Clean Code. On Jan 30, 9:13 pm, [email protected] wrote: > Hi! Sorry for the late reply... > > These are the books that I have read (or am reading) and would > consider "Must Reads." > > 1. Design Patterns (Gamma, Helm, Johnson, Vlissides) > 2. Refactoring (Fowler) > 3. Patterns of Enterprise Application Architecture (Fowler) > 4. Clean Code (Martin) > 5. Continuous Delivery (Humble, Farley) > > These are either on my "ToDo List" or have been highly recommended by > others: > 1. Working Effectively with Legacy Code (Feathers) > 2. Test Driven Development: By Example: (Beck) > 3. Domain Driven Design (Evans) > 4. The Principles of Product Development Flow (Reinertsen) > > There are many more good/great books out there, but this is my short list. > > Hope that helps. > > Mike > > On Jan 30, 2011 7:26pm, Ronald Woan <[email protected]> wrote: > > > Hey I still have a few of the Turbo Pascal manuals in Ziplocs along with > > Ultima maps that I had Lord British sign while in Austin. My most trashed > > book through use of all times is the first edition of Programming Perl. > > That much said, my favorites: > > Refactoring - Fowler, I had the book for a while but I lucked out and > > happened to be visiting a research team at Purdue, the same day Martin > > Fowler was giving a presentation and it finally clicked that it is like > > database schema normalization, almost a brainless activity that gives you > > the confidence that you don't have to have big upfront designDomain > > Driven Design - Evans - signed up for Eric's reading circle at OOPSLA for > > the book's release, that book combined with OOPSLA tribute to the > > Scandinavian School of Design made me realize that my 10 years of > > hardcore C++ and Smalltalk flirtations completely missed the point of the > > roots and promise of OO.Design Patterns - again a couple years of > > skimming and shelfware until I met John Vlissides at IBM Research and he > > mentored me and supported my organization at IBM with his own time > > despite health issues - after getting into it, I grasped the importance > > of a ubiquitous language among developers for discussing designs with all > > their assumptions and tradeoffsUNIX Network Programming, Advanced > > Programming in the UNIX Environment - Stevens - I probably copied almost > > all of the code from these books in real-life projects at some point, for > > later editions of the former I had the pleasure of helping Richard verify > > his samples on AIXEffective Java - Bloch - came at a point of my career > > that I was getting overconfident, huge kick in the pants to keep on > > learning, it is so well written > > About Face [3] - Cooper - first book that got me into interaction design > > and that usability is not voodooInnovator's Dilemma/Innovator's Solution > > (just pick up second, as it has enough of the first included)- > > Christenson - a business book but important for developers with any > > product management responsibility - why traditional good management > > practices doom companies over time and how to gain competitive advantage > > through deliberate innovation - completely explained all my frustrations > > with IBM management early in my careerRon > > -- > > You received this message because you are subscribed to the Google > > Groups "Seattle area Alt.Net" group. > > To post to this group, send email to [email protected]. > > To unsubscribe from this group, send email to > > [email protected]. > > For more options, visit this group at > >http://groups.google.com/group/altnetseattle?hl=en.
-- You received this message because you are subscribed to the Google Groups "Seattle area Alt.Net" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/altnetseattle?hl=en.
