Do something different

April 30, 2016

When I was in high school, I had a teacher that would often remind us (to the point of my annoyance), that the definition of insanity was doing the same thing over and over again but expecting different results. It’s an incredibly overused cliché, but it’s also incredibly helpful if you take it to heart.

When I first started programming I built an awesome text-based strategy game. Think Clash of Clans but without pictures. I started building it with a friend of mine and we based the majority of the game on an even older text-based game we had played years before. We eventually had a fully functioning game on our hands with built-in messaging, alliances, rankings, monetization, and even a battle simulation calculator for those hardcore players.

Since that project, I’ve started many side projects which I haven’t seen to full fruition. I’d show you the trail, but it’d just be a string of dead domains that never got renewed. Namecheap probably loves me.

Over time I noticed these projects often involved similar patterns:

  • Coding before design — As someone who codes for a living, it’s often an impulse to immediately jump to coding a solution. While I’m able to iterate designs quickly in the browser, I’ve often noticed it extremely slows my pace if I don’t have a guide. I’m more focused on how to get things to work instead of what or why. This leads me to fatigue on technical issues rather than stepping back to see the full picture.

  • Solo secrecy — Developers often have this habit of working on side projects. We also often have a hubris of what we think we can do alone and we hate telling anyone about them before they’re complete. For me, it’s often because I’m never quite satisfied with my work and am shy to show it off. This often means I don’t get external input. You don’t have to be a genius to know that’s a bad idea.

  • Fading motivation — Over time each side project eventually died off. Often times I wouldn’t even make it past a month of steady motivation. Sometimes it was roadblocks in code. Sometimes it was roadblocks in the idea (how would I get customers?). Sometimes the project was just no longer interesting.

Time for a change

It sucks having worked on these side projects and having virtually nothing to show for them. Yet, my desire for creating side projects hasn’t waned. Which is why earlier this year I started yet another side project.

But this time I’m trying something different. Many things I did in other side projects, I’m reversing.

I’m designing before I code.

I’m sharing the idea.

I’m doing user research.

I’m actively seeking help.

I’ve been working on it for months now.

So if you catch yourself doing the same thing, try something different.


P.S. For the curious, here’s the design I’m coding. I’ve had a teaser online for weeks, but I’m finally at a place that can warrant more details on the site. Introducing www.yourduet.com. Does this project interest you? Get in touch, I’d love to chat about it.