Quotes from Andrew Hunt

There is no such thing as a best solution, be it a tool, a language, or an operating system. There can only be systems that are more appropriate in a particular set of circumstances.

A user interface can be prototyped as a drawing on a whiteboard, as a nonfunctional mock-up drawn with a paint program, or with an interface builder.

Even if there's a fire raging (deadline, release date, trade show demo, etc.), you don't want to be the first one to make a mess.

Most software disasters start out too small to notice, and most project overruns happen a day at a time.

Pragmatic Programmers, however, tend to prefer using tracer bullets.

If you add layer upon layer, detail over detail, the painting becomes lost in the paint.

Prototyping is a learning experience. Its value lies not in the code produced, but in the lessons learned. That's really the point of prototyping.

Once they've agreed to the layout, you might throw it away and recode

Striving to better, oft we mar what's well. • King Lear 1.4

nonorthogonal systems are inherently more complex to change and control. When components of any system are highly interdependent, there is no such thing as a local fix.

EVERY PIECE OF KNOWLEDGE MUST HAVE A SINGLE, UNAMBIGUOUS, AUTHORITATIVE REPRESENTATION WITHIN A SYSTEM.

the real world just won't let us produce much that's truly perfect, particularly not bug-free software. Time, technology, and temperament all conspire against us.

you may not even need to code in order to prototype architecture—you can prototype on a whiteboard, with Post-it notes or index cards.

The scope and quality of the system you produce should be specified as part of that system's requirements.

You sketch out an overall shape, paint the underlying environment, then fill in the details. You constantly step back with a critical eye to view what you've done. Every now and then you'll throw a canvas away and start again.

If it's easy to reuse, people will. Create an environment that supports reuse.

expiring assets.[3] Your knowledge becomes out of date as new techniques, languages, and environments are developed.

Well, software doesn't quite work that way. Rather than construction, software is more like gardening—it is more organic than concrete. You plant many things in a garden according to an initial plan and conditions. Some thrive, others are destined to end up as compost.

There are no easy answers. There is no such thing as a best solution, be it a tool, a language, or an operating system. There can only be systems that are more appropriate in a particular set of circumstances.

If you were in a piña colada-making contest, these optimizations may make all the difference.

if you're using an exponential algorithm O(2n), you might want to make a cup of coffee—your routine should finish in about 10263 years. Let us know how the universe ends.

The process of learning will expand your thinking, opening you to new possibilities and new ways of doing things.

The cross-pollination of ideas is important; try to apply the lessons you've learned to your current project.

Talking to other people will help build your personal network, and you may surprise yourself by finding solutions to other, unrelated problems along the way.