Epiphany and Impact

Developer Diary Number 1

So, I'm working on several ideas, concurrently. An old client/friend of mine needs a new HTML5 complaint document management system, and there are lots of new options out there. Another one needs a CRM platform. Also, I'm looking at Edge Technology as a way to overcome the start-up costs of a new project, because I want to go into subscription software, rather than just code-for-hire.

I've finally discovered that code-for-hire is a trap. By the time you're done building testing and deploying the project you contracted for, made up the bills you incurred since the last project, and bridged until the next one, all the money you made is gone. You are just going from one project to the next, perpetually starving over the long term.

This time, I want to do it differently. I'm eating the time it takes to build the application myself, but then I'm going to subscribe it out. if you use it, you pay. every month. That way, I make some scratch, every month, and I'll know what projects need love, and what can be ignored.

The goal here would be to eventually be able to get enough subscription dollars to support myself and my family, and get to live the life I've always wanted... Building what I want, how I want to.

Anyway, the realization that hit me is that all these different project ideas I have all merge into one big project. Document Management and CRM simply become different departments, and a subscriber can create and configure as many of these as he wants.

All I need to do is monitor resource consumption. Users, and storage space. Do, with the help of my trusty business partner and sidekick, we've morphed all the various projects into one super-project, chock full of options, features, and capabilities, with a rather low startup costs, and a "Pay as you Go" subscription paradigm. Some serious refactoring has triggered a momentary halt in development, as the ramifications of this change become manifest.

As I build this monstrosity out, I want to use this blog space as an opportunity to share the thought process. Some entries will be about particular programming problems, others will be philosophical and theoretical. Maybe even a plug-in review every once in a while.

I'm also going to experiment with videotaping these, for posting on YouTube. So for all you TL;DR people, I'll read it to you!

Comments are welcome, and we'll gladly answer questions in the following blog post.