CANI : Java Glossary

2008-01-26 by Roedy Green ©1996-2008 Canadian Mind Products
index page for letter ⇒ punctuation 0-9 A B C D E F G H I J K L M N O P Q R S T U V W X Y Z (all)

CANI

Constant And Never-ending Improvement. Tony Robbins coined the acroynm to encapsulate the life philosophy Dr. W. (William) Edwards Deming, the man who taught the art of quality to the Japanese. It emphasises continual small improvements.

The Japanese have a single word kaizen for “constant and never-ending improvement”. The basic philosophy is, if all you do is improve one tiny aspect of your life every single day, you will achieve mastery in uncommon time.

This is how I approach the Java glossary, just constantly pruning it, and working to fix the thing about it I like least, in many small changes. I invite you to make your requests. You may have noticed my ongoing program to gradually replace the current ugliest icon on the site.

CANI Strategy For Writing Computer Programs

Here is my strategy for writing computer programs. It is based on 44 years of experience. My strategy is similar to extreme programming. My strategy could be called CANI which stands for Constant And Never-ending Improvement.

CANI Strategy For Writing Computer Programs
Strategy	Advantage
Write the simplest possible application first. Leave out all but the absolutely necessary features. Leave out the UI. Fake the UI with hard coded data initialisation.	If you implement a bare minimum to start, you find out about any show-stoppers early on.
Make and maintain a to do list of the most irritating things about your program. Weight flaws easy to fix slightly higher than they would normally place. Missing features go in the list as well, based on how irritating it is not to have them.	The process of improvement is endless. Whenever you have time to spend improving the program, you continue the same process. You can maintain that to do list any time you think of an improvement. Conceptually, the program is never finished.
Fix one problem at a time, working your way down the list.	If you add features one at a time, you are more likely to implement them in a well-encapsulated way. If you add features one at a time, you avoid brain overload. You focus on just a small aspect of the progam at time. Poor encapsulation becames immediately apparent when you go to add a new feature. You refactor before the mess has had a chance to metatastisise. You get in the habit of constant refactoring to make life easier to add the next new feature or change. If you add features one at a time, you are more likely to test them thoroughly.
Write Javadoc before you write the code.	Before you write the code and as you write the code is the time you are most aware of the alternative ways a method might be implemented. Now is the time to document that and disabuse the reader of the other possibilities.
Refactor as you go.	When you discover a bug, often you can prevent future such bugs by clever refactoring. You find this out at the earliest possible time, when the refactoring job is still fairly easy. If you refactor early, there is less work to do than if you let the problem fester. If you refactor early, you get the benefits early, making it easier to add the new features.
If you have users, show them your protypes and alpha versions, not just the finished product.	Early experience with the prototype will make you and your users smarter. The experience will inspire you to think of new features and discard or modify ones you planned to implement. It is better to find out about changes early before you waste time implementing.

recommend book⇒Dr. Deming : The American Who Taught the Japanese About Quality

paperback

hardcover

ISBN13:

ISBN10:

publisher:

Fireside

published:

1991-09-15

by:

Rafael Aguayo, W. Edwards Deming

One of the most most thought provoking books ever.

	abe books.co.uk	abe books.ca
	amazon.co.uk	amazon.ca
	abe books.de	chapters.indigo.ca
	amazon.de	abe books.com
	abe books.fr	amazon.com
	amazon.fr	barnes and noble.com
	abe books.it	powells.com
	iberlibro.com	abe books anz

Deming
design patterns
extreme programming
refactoring
software development model

	Please email your feedback for publication, errors, omissions, broken/redirected link reports and suggestions to improve this page to Roedy Green :
	Canadian Mind Products
	mindprod.com IP:[65.110.21.43]
	Your face IP:[38.103.63.59]	The information on this page is for non-military use only.
	You are visitor number 3,450.	Military use includes use by defence contractors.
	You can get a fresh copy of this page from:	or possibly from your local J: drive (Java virtual drive/mindprod.com website mirror)
	http://mindprod.com/jgloss/cani.html	J:\mindprod\jgloss\cani.html