| When I'd started my first job (after an ad-driven web app that went nowhere), I quickly found I wouldn't have much time for side projects. So I'd outsourced my little project to a talented dude from the east. This first project was to be measured with a financial goal -- 30,000$ a month. (was pretty naive) Hours per week: about 10. (learned a lot about documenting processes, instructions & ui flow's for an other dev.) Skills/Profile: worked on a ton of platforms. wrote emulators in high school. game engine developer. designed graphics hardware devices. published research papers. failed web startups. Success measurement: 30,000$ per month. (hit about 2,000$. liquidated. back to basics) ----- These days, my day job involves lots of consulting.
Side project profile: Hours per week: 40~ (I'm the core developer) Success measured: 100-1000~ active users. Financial goal: acquisition(s) in the 50-100,000$ range. (not tied to revenue / year) ----- Haven't hit any of my (almost) modest end-goals/exits yet. I've met a few of my 'on the road' milestones. They didn't make me feel any different. I love the process, and that keeps me going. If you're serious about forcing yourself into making an impact, find a bunch of target customers with a pain to be solved, talk to them, and promise them something with a deadline attached. I've found a lot of folks need the brute-force kickstart approach early on. |
If you're serious about forcing yourself into making an impact, find a bunch of target customers with a pain to be solved, talk to them, and promise them something with a deadline attached.
Oh, I wish my life were that simple. The people who most need/can benefit from one of my side projects are mostly openly hostile. I've spent a lot of time trying to make communication in-roads in the face of that situation. One of my goals is to try to start making more regular updates to the website in question in hopes that gets people thinking without getting their ire up so much (ie not as much as trying to actually talk to them tends to do). Eventually, I want to write an app for it (a simulation -- aka "game"). But a) the audience isn't ready for that and b) I don't know a progamming language. Recently, someone kind of suggested I start with a design doc to start documenting my ideas without needing to learn to program first.
I was quite ill for a very long time. So I spent a lot of time piddling around on the computer to occupy myself so I wouldn't go nuts but was unable to be very focused/productive. Now that I am healthier, I am trying to break some of those habits and figure out how to structure my time so I can gradually start accomplishing more.