3 tips for starting and finishing side projects

Published on January 22, 2019 - Tagged: #building

Follow me on twitter for more posts like this

Some of us like to make things for the web but everyone finds it super hard to find time to start and finish any side projects. If you’ve been thinking about something for a year but haven’t even started, here are some tips to help you start and finish more stuff!

1. Ship immediately

The very first thing you should do is ship the thing out to the world. Just write

<html>
  <head>
    <title>My Project</title>
  </head>
  <body>
    <h1>My Project</h1>
  </body>
</html>

in an index.html file and put it on Netlify or some other host you like.

> npm install netlify-cli -g
> netlify deploy --prod

Forget about the name, the domain, the technologies. Once you start shipping you will have a better understanding of how long the feature(s) you want will take to build and having the placeholder out there is incentive to finish.

See the Zeigarnik effect about unfinished tasks: https://en.wikipedia.org/wiki/Zeigarnik_effect

2. Reduce scope to one feature

We often assume projects and tasks will be easier and shorter than they end up. Unless you’re a genius estimator have probably seen this in your work. If you’re having trouble finishing side projects you need reduce scope to something that will take a maximum of 2-3 evening of work.

That could be as small as just launching that index.html on Netlify if you have never done that before. Think small, really, really small. Much smaller than what you might volunteer to do at work.

At the very most choose one feature to build, not an app or a full website. Just build the feature as simply as possible. Use a Google sheet to simulate algorithms and data.

See the planning fallacy on optimism bias in humans: https://en.wikipedia.org/wiki/Planning_fallacy

3. No Shiny objects!

Don’t use any new-to-you shiny technologies when building your feature. You WILL get lost in it. (Unless your aim is to learn the new technology then go for it - but limit yourself to ONE new tech).

Almost every new library will have common accompanying libraries or technology and you will follow a trail down the rabbit hole until you get bored and move on.

Go with what you know and get the feature out! You can refactor it in to the new technology AFTER you have a useful side project.

See a package.json or NuGet packages.json on any project!

Finally

Don’t forget to reward yourself when you get it done! 🍷 🍫 🥕

Darragh ORiordan

Hi! I'm Darragh ORiordan.

I live and work in Sydney, Australia building supporting happy teams that create high quality software for the web.

I also make tools for busy developers! Do you have a new M1 Mac to setup? Have you ever spent a week getting your dev environment just right?

My DevShell tooling will save you 30+ hours configuring your dev environment with all the best modern tools. Get it here

https://darraghoriordan.gumroad.com/l/devshell


Read more articles like this one...

List of article summaries

#building

Startup Weekend

Wow, it’s a week after Startup Weekend Auckland. I’ve had time to get my thoughts straight about the whole experience. I learned a hell of a lot of positive lessons about idea validation, about myself and about working in teams.