Doing it yourself
Sunday, January 31st, 2010When I take on a project, I tend to just keep plugging away at the whole thing one chunk at a time. If I come across a chunk that I don’t know how to do, the internet is my friend and I figure it out. Of course, this can lead to me taking a couple weeks to a month or more to get something done. So if you take a look at my site, don’t be surprised if it hasn’t changed in a while. Changes are also delayed because I attempt to have some sort of life and time to spend with my son.
Right now I’m working on building a home-grown menu function. The concept is easy, and there are only so many things to keep track of, but I’ve only hacked other peoples javascript or written small simple functions. I’d like to write this one for myself so that I understand the underpinnings to the system. Only by understanding it fully can I begin to improve it. It’s taking time. This dude over at ihumanable has a nice post to this effect.
For a bootstrapped business, I think this is an appropriate way to go. It takes minimum investment and the end result is that I know what is going on. Unfortunately, it can tend to drag things out. Maybe my problem is that I am not that good at searching the web, but I can only spend so much time searching for something that does what I need without getting the feeling that I’m wasting time. Thus I churn away at a problem until it’s done to my satisfaction. It may be a little buggy, but it works for most cases. At some point I’ll get back to the functions that are buggy.
With that said, if you happen to come across a bug, please drop me a note. I have a long list of bugs and improvements that I attempt to work my way through as fast as possible. Unfortunately, I tend to add improvements faster than I really ought to. Right now, though, I’m trying to work through the critical path from 0 website income to lots. So some of the smaller bugs are going to go on the back burner.
Some interesting sites
