Not working is not the same as FAILING

Over the past few weeks I’ve been writing a “Didn’t Work Wednesday” series and covering some of the many mistakes I made back when I was focusing on Supermug.

If you’ve been reading along, you already know that there were plenty of mistakes (and I’ve still got more I can write about in future posts)…but I thought today I would take a few minutes to point out that there were a few really good things that came out of all that work as well.

First - the obvious thing is that I was diligently working towards my 10,000 hours of becoming a half-way decent programmer.

Second - I was also figuring out, VERY SLOWLY, how this whole ‘business’ thing actually worked…or at the very least, lots of ways that it absolutely didn’t.

But more important, it presented the opportunity for other projects and businesses to emerge.

One of which was - which also, eventually, didn’t work (and I’ll be covering that in my series eventually too).

The other was - which was probably my greatest personal business success to-date (at least financially).

Neither of these projects or businesses exist anymore (for various reasons) - but both were huge parts of my evolution, thinking, and experience…and both were directly born out of all the time, energy, and resources I initially poured into the Supermug idea.

So I’m focusing the series on mistakes I made (and hope that we all can avoid in the future), but I wanted to point out that making mistakes, and having things “not work” is not at all the same thing as “failing” and also isn’t an entirely bad thing when you take the long view.

Don’t let it get you down. Take the long view.

This post has received 39 loves.


This is the personal blog of Kevin Marshall (a.k.a Falicon) where he often digs into side projects he's working on for and other random thoughts he's got on his mind.

Kevin has a day job as CTO of Veritonic and is spending nights & weekends hacking on Share Game Tape. You can also check out some of his open source code on GitHub or connect with him on Twitter @falicon or via email at kevin at

If you have comments, thoughts, or want to respond to something you see here I would encourage you to respond via a post on your own blog (and then let me know about the link via one of the routes mentioned above).