Programmer's Creed: The Mark of Quality
- I will not begin the design phase until the user requirements have been unanimously agreed upon by all users, and etched onto large stone tablets.
- I will not begin development until the design is signed off, preferably in blood.
- Issues that arise during testing will be recorded in the issue management system, and the relevant developer shall be notified, in writing, before he or she is taken out and flogged, not after.
- Product upgrades will not be released into the production environment until the quality assurance manager has scheduled a time to place his or her head on the correct chopping block, and the axman or axewoman has verified that the ax is indeed sharp.
Feeling very bitter and cynical today.
Add or view comments about this page
|
Articles
Just Wally
The Correct Order for a First Time Viewing of The Lord Of The Rings
A new era for Android.
Mind-boggling Demo of New Gaming Genre, aka Folder-Based Hangman, aka Fun with Recursion
Got CSV in your javascript? Use agnes.
Complete secretGeek Archives
TimeSnapper: automatic screenshot journal
NimbleText: Code Generator, Text Manipulator, Data Extractor
25 steps for building a Micro-ISV
3 Minute Guide Series
Universal Troubleshooting Checklist
Top 10 SecretGeek articles
ShinyPower Now at CodePlex
RealTime Online CSS Editor
Gradient Maker
How to be depressed
You are not inadequate.
Recommended Reading
 the little schemer
The Best Software Writing I
The Business Of Software (Eric Sink)
Recommended blogs
Jeff Atwood
Joseph Cooney
Phil Haack
Scott Hanselman
Julia Lerman
Rhys Parry
Joel Pobar
Thomas White
OJ Reeves
Eric Sink
Aggregated Links
proggit
dzone
hacker news
dot net kicks
Human Link Machines
interesting finds
a continuous learner's weblog
arjan's world
weekly link post
LogEnvy - event logs made sexy
Computer, Unlocked. A rapid computer customization resource
PhysioTec, Brisbane Specialist Physiotherapy & Pilates
|
|
|