Mike Levin SEO

Future-proof your technology-skills with Linux, Python, vim & git... and me!


by Mike Levin SEO & Datamaster, 05/05/2008

miklevin.com - May 2008

Monday, May 5

After 30-some years of false-starts with entrepreneurial-type ventures, I’m finally deciding to draw the line in the sand and make it happen. I’m still working full-time for a main employer, and will be putting in over-the-top efforts for them, but that’s because I’m a professional search engine optimizer, and I need to stay at the peek of my game for whatever I do for myself as well.

It’ll be taking the slow-build type approach, funded with my own personal cash, because it’s not going to take that much in terms of servers or hired programming skill. I bring all that to the table myself. My server programming techniques are efficient-or-die. In other words, I program the app to the server technology that I’m using, and can choose from incredible server-hardware-for-the-money, cheap traditional ISP hosts, or the fangled new computing clouds from Amazon and Google. It’s getting really cheap to innovate and eat the big guys’ lunch, because that type of agility gets cracked down on by committee. I’ll be keeping all of my endeavors compatible with my employer, so when they tune into what they’ve actually got as an asset in their company, I will be able to easily adapt my outside projects to benefit them, as sort of a partnership. But I’ll be applying for all my patents on my own from now on.

First, I have to start with a really big idea. In fact, I have to start with an idea that has it’s own success embedded into it, through having a pre-existing market-demand, whether anyone realizes it or not, and a self-fueling viral aspect, where the users of the product become it’s biggest word-of-mouth advocates. People have to LOVE it. People have to tell others about it. Barrier to entry needs to be low, and the payback for hopping on the bandwagon needs to be high.

I can’t let technical challenges stand in my way, NOR can I let group or interpersonal dynamics stand in my way. Multi-way dynamics kills projects, right as they need momentum. The desire to choose the latest, greatest, but as-of-yet unfamiliar programming framework kills momentum. I cannot let momentum be killed on either of those fronts this time. I will ironically keep my cards very close to my vest, and blog about it publicly as I go. This is not only a lesson in how things get done in a Web 2.0 world, but I’m also planning for it to be a lesson in altruism, sharing, open source, and programming and entrepreneurialism as sort of a performance art.

The way the websites relate to eachother finally has to be nailed down, so each time I post, I know which site I’m plugging it into. My method for writing needs to be nailed down, so I don’t have to figure out what application, tool, website, or whatver to fire up each time I start writing. This approach has merit, because it’s able to be published directly as a Google Doc, preserving all of it’s formatting, but is also able to be blog-posted directly into Blogger, thus auto-marketing it through superior search engine optimization, the blog ping posts, and the rockin’ RSS feeds.