Win a copy of Head First Android this week in the Android forum!
    Bookmark Topic Watch Topic
  • New Topic
programming forums Java Mobile Certification Databases Caching Books Engineering Micro Controllers OS Languages Paradigms IDEs Build Tools Frameworks Application Servers Open Source This Site Careers Other Pie Elite all forums
this forum made possible by our volunteer staff, including ...
Marshals:
  • Campbell Ritchie
  • Paul Clapham
  • Ron McLeod
  • Tim Cooke
  • Junilu Lacar
Sheriffs:
  • Rob Spoor
  • Devaka Cooray
  • Jeanne Boyarsky
Saloon Keepers:
  • Jesse Silverman
  • Stephan van Hulst
  • Tim Moores
  • Carey Brown
  • Tim Holloway
Bartenders:
  • Jj Roberts
  • Al Hobbs
  • Piet Souris
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Report post to moderator

Image source leanpub.com

Title: Understanding the 4 Rules of Simple Design
Author: Corey Haines
Publisher: Leanpub

Summary

The only thing we truly know about software development is that we can expect changes to our system. Through concrete examples, let's explore ways to build flexible, adaptable software systems by better understanding Kent Beck's 4 Rules of Simple Design.


From the publisher
  • Sample

  • Where to get it?
  • Leanpub


  • COMMENTS:
     
    Sheriff
    Posts: 8102
    571
    Mac OS X VI Editor BSD Linux
    • Mark post as helpful
    • send pies
      Number of slices to send:
      Optional 'thank-you' note:
    • Report post to moderator
    I give this book 10 out of 10 horseshoes.

    There are books which shape the way you think about the programming. This book is one of those.
    I’m glad I’ve been introduced to it by Junilu Lacar, moderator here at coderanch.

    Book is only 88 pages long including its cover, contents page and other typical (I’ll call them administrative) pages. Genuine. Because of Zak.

    So what’s left? Well, much more than I thought. I read this book 3 times, actually 4 already, and each time I was reading it, I found some new lessons to perceive, I guess that is because each time I was working on a different programming problem, so I extracted information I needed at a particular point in time.

    Book is organised in a short discussions where reader is being taught to think about the instantaneous design decisions.

    What this book is about? In short – about the aspirations for better computer systems design, about the expressiveness of the ideas you communicate, and about the working software, where passing tests are the only proof. TDD mindset is widely spread and applied across the book.

    Corey Haines wrote this book in a subtle way, which in my opinion can fulfill various technical level developers expectations and most likely exceeds them.

    To convey book’s conciseness, I’ll stop right here. Really recommend to read and re-read this book.
     
    You showed up just in time for the waffles! And this tiny ad:
    Building a Better World in your Backyard by Paul Wheaton and Shawn Klassen-Koop
    https://coderanch.com/wiki/718759/books/Building-World-Backyard-Paul-Wheaton
      Bookmark Topic Watch Topic
    • New Topic