New Experiment – The Daily Coder

I’ve been trying to get my coding blog going bit by bit but I’ve struggled with it a bit – – perhaps it’s due to to not enough focus, perhaps it’s due to not having enough time, whatever the case, I’m starting a new project with this blog at it’s core.

For the month of June, I will be committing to doing an hour of code a day and blogging about it.

The rules are;

  • One hour of day of code per day.
  • Cannot be part of a professional project – must be my own project.
  • Learning doesn’t count, i.e., watching a PluralSight video, it must be actual coding.
  • Must write about it each day.

I don’t code every day or rather push it off more than anything else because that part of me worries that it’s going to be too hard to get back into and what I create won’t be anything of worthwhile value.

So let’s see what I can do – the experiment starts tomorrow.

Sharing your Work

I wrote a LinkedIn article about a month ago and then decided to share it across a number of groups – groups that had 70,000+ members associated to them.

As I wrote some clever summary I worried about how it would be perceived, what would people think?  Would they love it?  Would they hate it?  Would they tear it apart?

I could feel my brow furrowing and sweat starting to form as I clicked “Post”.

And then I waited…


Still waiting…

Nothing happened, a few people liked it, but that was about it.

No viral sensation, no interviews, no public firing, nothing.

The world kept spinning, my day carried on and I’ve kept on writing.

Moral of the story – You’ll be okay, don’t over think it, just do it, share it, see what comes back – and move on.

Sharing your work to others the first time is never easy because we focus on the rejection first and the acceptance last.

Will everyone like your work?  No.

Now that you know the answer will you still share it?

Great, go do it.


It’s a little Rough around the Edges


That means there is still work to do and you’re still plowing through to make it happen.

That means that despite your setbacks, whether they are internally driven or externally received, you are not stopping.

That means that when you first compile, it doesn’t always work and you need to put a little more polish into the finished product.

That means you are still going.

Being rough around the edges means there is still work to do, pieces to fix, problems to address – it means perfection isn’t there, but the components and ingredients are.

It simply means – we have a little more work to do and we shouldn’t give up – it’s too early in the game.

It’s also a reminder that the game is never over, sometimes its just begun.

What’s In A Mentor?

I wrote an article awhile back on what I think it takes to be a Mentor to someone.

What is not said in this article is that I learned all of these traits many years ago, when I was still in University, watching a telephone conversation take place that to this day I never forgotten and convey to others.

The approach, skill, patience and integrity in that one interaction taught me what no book ever could hope to achieve and what I endeavour to do with others.

I don’t if this person will see this today, but they have a profound impact on me and today, on their birthday, I say thank you to them for being a great Mentor to me.

I Need that Fix

I need my coding fix to keep the logical part of my brain happy.

I need my writing fix to get out everything I have in my head.

I need my entrepreneurial fix to engage that feeling of starting something and growing it.

I need my sales fix that drives me to reach out and network with people.

I need my leadership fix when coaching and working with teams.

I need my exhaustion fix when I finish going for a run.

I need my building fix when I try to build something with my hands, admiring the calluses I have earned at the end of the day.

I need my humble fix when I try something new and keep failing no matter my level of effort.

I need that family fix where I get to step back and be amazed by all they can do.

We all have a variety of fixes we need in our life, the goal should never be to focus on just one, but instead to understand what ones we need and how to craft a life around that.