Shake down cruise

Ahhh the smell of fresh procedural code in the evening… smells like… time that could have been spent getting more done in an object oriented environment.

One of the bad habits I’ve picked up working as a lone-wolf is my approach to limited-use, batch process-oriented code. I tend to build these huge sweaty inline monsters, with little worry about beauty or serviceability. Knowing almost everything I need to know about the language I’m working with, the last challenge becomes building a large app top to bottom, then firing it up without prior testing to see how few defects I coded. There have been moderately complex apps I have done this with where it ran perfectly the first time, but for the most part there are usually a couple things I will mess up.

The current large batch processing app occupying most of my off-time is of course the Manila-to-WordPress-O-Matic and today I pretty much finished every part of the program, looked it over a bit and decided to start in on debugging the code. Suffice it to say I am apparently pretty rusty on my UserTalk skills by the towering defects in the process, only about 10% of which I could not have seen coming. Oh well, good thing I got on this before I forgot how to code Frontiel altogether.

At this point the code creates, on the WordPress site, all needed member logins, creates all news post categories and posts all Manila Gems to WordPress uploads.

More soon.