Hacker News new | ask | show | jobs
by Toss8675309 2363 days ago
Absolutely

0. Make sure your house is in financial order. If you are a habitual user of credit cards, have high monthly debt obligations, and no saving, before you even think about going out on your own, change that.

1. Audit your ability to estimate time and hit deadlines. Most developers are rubbish at knowing how long a project will take, even a small one. Make sure you can hit a deadline. This is more important at the outset than your ability to estimate.

2. Start thinking about yourself as a provider of solutions rather than as a developer. You happen to have the superpower of being able to create software, but that's just a tool. Real value is delivered by providing solutions to problems within a business.

I could write pages on each of these points, if you have further questions I'm happy to answer.

Getting your first client, a couple ideas: - Talk to small marketing / ad agencies in your town that won't have internal developers, offering to put some technical muscle behind what they're doing for their clients. - Look for people in your personal network that could benefit from your superpower. Offer to build tools to solve the issues they're dealing with.

These are super generic ideas, I can offer better and more targeted advice if I know a little more about you and your skillset. Hit me up at batmaniac@gmail.com.

1 comments

Hey this is really amazing advice, thanks a ton for sharing! I'll definitely reach out with more questions! Especially the time estimation part. Even during my day job I find I tend to underestimate. Over estimating is probably more desirable in this line of work.
Yeah, time estimation is really tough. When I started I figured out I just needed to take my time estimate and double it. Then I got really analytical about it. Now I take my gut estimate and add 20%, but I've also gotten away from time-based billing into value-based estimating (that's a whole other very deep subject).

The "really analytical" phase wasn't too crazy by HN standards:

- Break the complete project in Pivotal Tracker down to stories no larger than 8 points

- Track the time spent on each story in Harvest

- Use that data to figure out how much time a given point score equated to, along with variance.

- Work to reduce the variance.

I should also say...I've been estimating software for, good god, I haven't done this math lately, 18 fucking years. Do anything repeatedly that long, your instincts become pretty solid.