I'm trying! My main concern is the years of code I have out there that has zero documentation.
But I've got A Plan. Everytime I have to reuse/rewrite some piece of code, I'm going to Do It Right as far as documentation and diagramming. Since the majority of my job is adding more features on to software I've already written, this should eventually cover the majority of my sins.
Hmmm.
Well the presentation I am referring to was given by Tom Bress at NI week 2009. It is titled
"From spaghetti code to State Machines: One Man's Journey through the NI Certification Process"
http://www.ni.com/niweek/summit_presentations.htm
Dan
Or even better just superimpose them. I can somehow see that only the Report instanziation (spellcheck) has to be changed, but a new class OpenOfficeReport could override the Office Report Toolkit.
This would also limit the number of functions you need to create.
Ton