Sweet Source

One of the problems I had with software development was finding something to make. Being more technical than creative, I only ever came up with the most mundane projects. And on top of that, I needed the source-code to be well-ordered with a logical flow, the functionality couldn’t be hacked together — if it was going to be kludgy, then I wanted no part of it — it had to be clean and tidy.

I tried my hand at commercial software development for a few years in the “shareware” markets. I made some sales but nothing major. Eventually when I needed some real money, I found a work-at-home programming job as an independent contractor developing websites. I was more experienced creating desktop software, so it took a little bit to get comfortable writing backend code for websites and tying them to databases.

Through subcontracting and sometimes sub-subcontracting, I even did work for a few large well-known companies. I had to be on conference calls and act all business-y. Prior to this, I had worked part-time at my father’s business doing computer related stuff, so it was somewhat familiar, the calls and talking to business people and being the tech guy and such.

But in the end, clients were no better at coming up with interesting projects to work on than I was. So with a lagging interest, combined with my persnickety approach to programming, it just didn’t work out in the end, me and software development. I can’t say I miss it, but I can’t say I’d never go back either. And technically, I still sell a small amount of software but no longer update it, so it’s likely to become obsolete.