Hansel and Gretel wondered, looking back behind them only to see a Goose gaining weight from all the bread it was eating.

 

 

Often when I’m in a project, such as the Morse Code Decoder, that right before releasing something that I find I get lost.  Don’t know what to do next, it seems that there is so much to do.  So I end up looking around and trying to figure out what to do next, or what needs to be done for the project to be released.  

 

It is during those times I have just said forget it and just released it when what I have done and just hope for the best.  Sometimes it works, but most of the time it doesn’t, just because I just want it done and want to move on to the next project. 

 

Why would I do such a dumb thing?  Well for one I just really don’t know how to finish a project properly, set it up so that I can hand it off to, who or what, ever and have it ready for the next round of upgrades and it it is neat and tidy.  Man, that would be nice to have the done for once.  

 

Personally, the hardest part of any project is the last 20% of it.  That is the most tedious part of any project.  Writing documentation, describing what it is to do.  Polishing the way it looks, making sure all the I’s are dotted and the T’s are crossed.  Did I mention I would prefer to just program? 

 

However, the last 20% is the most important, this helps with future work on the current project.

It was easier to get back into the project if there was documentation. 

 

Many times when looking at old code,  that actually was clever.  I would not recognize who wrote it, when 6 months earlier it was me who wrote it. So often I had to move to other work, then come back to it later, I forgot a lot of what I did.

 

Writing what the app does or what a algorithm does doesn’t have to be done all at once it can be done over time, when the code was written or, when you are thinking of what the screen or app will do.  I’m still working on that.