Seize the storm

Development is now over 160 hours - but what does that mean, right?  Well, I’ve implemented a completely new feature.  It didn’t take too long to implement and though I’m happy it’s implemented and the feature will give people a better sense of organization -  the feature doesn’t do as much as I wished it would.  The root of the problem there is more related to standards of acceptable use of the feature.  I wish I could divulge more - but you know how that goes.

I delved into a new feature about a week ago, drawing out some design on my new whiteboard (my first actual business purchase - hahaha).  As I sat down at my computer, I realized the need to go back to the guts of my program and restructure the settings portion.  This rewrite is now complete however it broke a bunch of stuff in other areas, which is natural when messing with such a core feature.  Cliche alert - sometimes you have to rebreak the bone to get it to heal straight (or however that goes).  I am really excited about this though, because how I’ve restructured the settings of Photo Ops has set me up for the true heart of where I want to go with the program.

All this rewriting is pretty painful for me, and really for any developer - as we’re admitting to ourselves that the initial design wasn’t good enough.  Closer to release, I will be facing a similar battle when I go back and fight the efficiency monster.  There are some portions of the program that seem to lag, so I will be going back and fine-tuning the feature as I know P.O. is not going to be running on Pentium 4’s all the time.

My family and friends are continually asking how things are going and I always reply, “I’ve got so much more to do, but it’s coming along.”