Andrew Hunt Famous Quotes
Reading Andrew Hunt quotes, download and share images of famous quotes by Andrew Hunt. Righ click to see or save pictures of Andrew Hunt quotes that you can use as your wallpaper for free.
As Pragmatic Programmers, our base material isn't wood or iron, it's knowledge. We gather requirements as knowledge, and then express that knowledge in our designs, implementations, tests, and documents.
We who cut mere stones must always be envisioning cathedrals.
In addition, build dependencies may not be the same as test dependencies, and you may need separate hierarchies.
Documenting the reasons behind requirements will give your team invaluable information when making daily implementation decisions.
You Can't Write Perfect Software. Did that hurt? It shouldn't. Accept it as an axiom of life. Embrace it. Celebrate it. Because perfect software doesn't exist. No one in the brief history of computing has ever written a piece of perfect software. It's unlikely that you'll be the first. And unless you accept this as a fact, you'll end up wasting time and energy chasing an impossible dream.
In an article in the April 1999 CACM, Robert Glass summarizes research that seems to indicate that, while code inspection is effective, conducting reviews in meetings is not.
Just be aware that you reach a point of diminishing, or even negative, returns as the specifications get more and more detailed.
But while you can always write 'spaghetti code' in a procedural language, object-oriented languages used poorly can add meatballs to your spaghetti.
If you work closely with your users, sharing their expectations and communicating what you're doing, then there will be few surprises when the project gets delivered. This is a BAD THING. Try to surprise your users. Not scare them, mind you, but /delight/ them.
...maintaining good regression tests is the key to refactoring with confidence.
More testing should be done automatically. It's important to note that by "automatically" we meant that the test /results/ are interpreted automatically as well.
Don't gloss over a routine or piece of code involved in the bug because you "know" it works. Prove it. Prove it in this context, with this data, with these boundary conditions.
