-->

Monday, July 1, 2013

Coder's Log...How and Why You Should Maintain Them

Continuing from a post I made to young graduates on giving an internship to yourself, I thought I may as well give an example of how to do so.

LOG YOUR PROGRESS

With every iteration of one's work, its important to log and chart yourself, somehow, someway. In practicing what I preach, I figured I'd grant an example right here, as I would go about on the exciting journey of developing an atm machine (more on that in a future post):

~~~
Progress Log - June 27th and 30th
I continue to make forward progress on the bank simulation synthesis project. Software Development Guide now 10 pages and progressing smoothly on the accordance to my assigned timetable of my first iteration. 

Additional Notes
I wish I could move this a bit further, but as the only person on the job, I'll have to forgive myself.

Progress Log - July 1st
Practiced some CSS coding as warm up. Tested and successfully ran my first proof-of-concept GUI for Android. I belief I now understand how to make any program I've previously written run on a phone. Adapting to Eclipse has proven not as complex as I thought, and continued practice will assuredly serve to make me all the more comfortable.

But first things first. Time to consult the SDLC again and recall my next step.

Next Goal Note: 
Incorporate a database management system into the project...time for more research. As well as updates to my UX diagrams in light of new tools I'm made aware of.

~~
A good log document keeps it simple.  If you'll notice, this entry also backlogged for several days. So its not like you have to make an account every single day, but simply, that you jot as much as you can periodically. When you do so, it'll do wonders for keeping you motivated and on task.

More importantly, it'll work wonders on the concepts of TESTING and ITERATION. But more on that for another day. ;)

~David Noble Morris~