A. HUNT AND D. THOMAS

 
Some things are better done than described....Here's a challenge for you. Write a short description that tells someone how to tie bows in their shoelaces. Go on, try it!
- A. Hunt and D. Thomas , The Pragmatic Programmer: From Journeyman to Master by Andrew Hunt, David Thomas, Ward Cunningham (Preface) , ISBN: 020161622X
We feel that the only way to develop software reliably, and to make our developments easier to understand and maintain, is to follow what we call the DRY principle: Every piece of knowledge must have a single, unambiguous, authoritative representation within a system. Why do we call it DRY? DRY - Don't Repeat Yourself. The alternative is to have the same thing expressed in two or more places. If you change one, you have to remember to change the others...It isn't a question of whether you'll remember: it's a question of when you will forget.
- A. Hunt and D. Thomas , The Pragmatic Programmer: From Journeyman to Master by Andrew Hunt, David Thomas, Ward Cunningham (Preface) , ISBN: 020161622X
Requirements are not architecture. Requirements are not design, nor are they the user interface. Requirements are need.
- A. Hunt and D. Thomas , The Pragmatic Programmer: From Journeyman to Master by Andrew Hunt, David Thomas, Ward Cunningham (Preface) , ISBN: 020161622X
The art of programming lies in that nether region between the hopeful wishes of an elegant architecture and the hard grindstone of technical details.
- A. Hunt and D. Thomas - in IEEE Software magazine's "Software Construction" column by Andy Hunt and Dave Thomas.