“I don’t have time to code in my free time”
I convinced myself this was true until I joined Ship 30 for 30. I saw how having sacred hours to write an atomic essay was effective. So I applied what I learned from Ship 30 to building a daily coding habit.
Here's what I've learned since I started in mid-January:
1) Consistency doesn’t mean every day
It's OK to take a few days off.
I need the time off to avoid burning out or spending time with family and friends. Coding for an hour should never be my #1 priority. But I shouldn't develop a habit of missing days consistently.
As long as I'm being consistent over a long period of time, I'm happy.
2) The quality of work isn't important to me
If at the end of the coding session I create something trivial, then it's OK.
I care about putting the reps in, not the quality of the work. Today I might create something trivial. Tomorrow it might turn into something complex if I build off of it.
Just put in the reps 💪.
3) Give yourself permission to do things you thought you couldn't do
I thought I had to code for a full hour.
But there were days I didn't feel motivated to do so. I didn't want to miss a day, so I changed the rule from code for an hour to code for up to an hour. I gave myself permission to take it easy when I needed to.
Sometimes coding for 20 minutes brought back my motivation to code the full hour.