Pic courtesy of Cambodia4kids.org Beth Kanter

I’ve failed to code every day, so…

I have been trying to learn to code every day through the #100DaysofCode campaign. I thought I had it all down. At least 30 minutes a day would suffice. Well, it was tough.

Yesterday was supposed to be Day 12 for me. But Day 12 had a packed itinerary. And on this part of the big blue marble, it was the eve of a festivity. Also, I had a few interviews — freelancing is all about hustling.

When I reached home, I was tired. Sleep was a comfortable option. I didn’t even hit the gym.

Here’s what I’ve learned so far that led me to… well… fail:

Always plan ahead

This is obvious. I knew I have a busy day ahead. But I didn’t bother planning. I thought I could just slot coding into my schedule like as if I was going to eat lunch or dinner, or take a shower.

It doesn’t work that way. I have to look at my schedule and find time to do the work uninterrupted.

Learn in chunks

My most productive days were when I broke my studying into chunks.

So 15-minute sessions work well for me. I was surprised by how much I learned. I accumulated an hour’s worth of coding. It was easier to digest. Better than doing a 30-minute session straight.

Be flexible

With so much to do, I knew I had to be flexible with my approach. I have an iPad and a desktop. My tablet means I can take my studies with me.

The problem was I got comfortable with my desktop and insisted that I had to do the bulk of my studies on it. Well, that didn’t go according to plan.

Never give up

I always believe that the things I love the most are the hardest to accomplish. That makes them desirable, worthy of a lover’s pursuit.

So what do I do? I have declared to the world, including you dear reader, that I will code every day… and I plan to fulfill it.

Here’s pressing the reset button. It’s time to get back to Day 1.

Like what you read? Give Emmanuel Surendra a round of applause.

From a quick cheer to a standing ovation, clap to show how much you enjoyed this story.