• Post Reply 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
  • Jeanne Boyarsky
  • Ron McLeod
  • Paul Clapham
  • Liutauras Vilda
Sheriffs:
  • paul wheaton
  • Rob Spoor
  • Devaka Cooray
Saloon Keepers:
  • Stephan van Hulst
  • Tim Holloway
  • Carey Brown
  • Frits Walraven
  • Tim Moores
Bartenders:
  • Mikalai Zaikin

A good design book?

 
Ranch Hand
Posts: 70
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
I have been trying for a long time and with many failures to find a book that discusses how to properly design full programs. Previous programs I have completed seem to start out well, but tend to show their problems only after too much work has been done. I usually end up spending countless hours to redesigning to accomodate a feature I should have, but never anticipated. I understand the importance of creating a good design before programming, but have no idea where exactly to start and the necessary steps towards program completion. I purchased many books that discuss steps on how to create a very specific program, but no books that use a more broad-scoped approach. Can anyone recommend a good book that can help me?
BTW, this is my first time to a design specific forum. This is great!!
 
author
Posts: 799
5
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
Bob Martin's book Agile Software Development is a good balance between design and realization of design in code. The problem with many design books is they don't discuss the implications of design. The problem with that is you need to learn when you have a bad design. While there are principles and such that guide what a good design is (Martin discusses these), often you won't know that you have a bad design until you code it.
To be a good developer means you need a solid understanding of both design and construction--each impacts the other. The Martin book explains this relationship better than any other book out there.
Also, even if you could come up with a perfect design up front, poor construction would cause it to disintegrate over time. I highly recommend Martin Fowler's book Refactoring to understand how to keep your code clean; I also recommend the upcoming edition of Code Complete (Steve McConnell).
-Jeff-
 
Ranch Hand
Posts: 47
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
I have been reading Eric Evans book, "Domain-Driven Design". It has been illuminating!
 
Tyler Jordan
Ranch Hand
Posts: 70
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
Thanks for the suggestions! The reviews on Amazon and other sites are very misleading. I sometimes wonder if the people who write those reviews actually read the book!
 
With a little knowledge, a cast iron skillet is non-stick and lasts a lifetime.
reply
    Bookmark Topic Watch Topic
  • New Topic