Commands we wish could rule
If we could add a command to improve computing, what would we wish for?
Here is a list of commands that we may want to rule in future
This command would generate an uncontrollable urge in all managers in
your company to re-instate all the software training budgets they
All software users would gain a ravenous appetite to read all
documentation available on the command of their choice.
All the dry documentation would now be fun to read and understandable.
When given a desired result, its_in_there will be able to list many
examples of getting what you want.
A software user will gain the will and courage to test and try out the
software. The software user will become confident that the job -can- be
with the software.
When talking with the software vendor, the customer will be completely
coherent, logical and easy to understand.
The software users 10 years of experience working with package A will
be converted into 10 years of experience in working with package B.
This will sort out all user errors and re-instruct the user before a
bug is submitted.
This command will instruct the software vendor on why it is a bug, not
a user error.
The software vendor will have infinite resources to fix the customers
problems in a matter of seconds.
Put an enhancement request on top of the list of commands to be added
in the next rev. (modifier of infinite_resources)
This would merge the technology of graphical user interfaces with great
No matter the schedule, problem or blame, everyone remains cool calm
This would be invoked during the design phase of software.
Quality would become part of the design, not an afterthought.
© Val Hubbard
Commands we wish could rule last updated April 8, 2000.
This page last update March 22, 2011
These rules do not reference any specific person, company or
software package. They are comical exaggerations of the occurrences of
everyday life in the field of software. Any relation to events anywhere
past, present or future is entirely coincidental.