I've noticed that most people who do the #100DaysOfCode challenge are beginners learning to code. I've been coding for many years, so I wasn't sure if it was for me.

Here's why I've decided to start the challenge:

1. Play With Cool New Toys

There are so many fun developer tools that I haven't had a chance to try. For example, @vivgui told me about the joys of Tailwind CSS back in 2018, and I only got around to learning it a few days ago. Whoa, its CSS classes make composing UIs so much fun! There's also collaborative JS coding tool Glitch, which @danielfeldroy just got me into, and its cousin Observable for JS notebooks. And there's the realtime GraphQL engine Hasura which I'm eager to play with more.

2. Make Fun Stuff

Making stuff is fun. If I can't be at my local makerspace making art on the laser cutter, or in my art studio experimenting with messy mixed media painting, then at least I can code.

The Hard Part

I'm not sure if an hour a day is really doable for me. The toddler, business, family obligations, and stress are already leaving me exhausted. I'll try for an hour, but if some days I can only do 10 minutes, that's still better than skipping a day.

Overall Goal: Coding as Play

It's easy to get caught up in the mentality of "Coding is work." My intention with this challenge is for it to be fun experimentation and play. If it's not fun, I'll stop doing it. I'm hoping it'll help me make time for personal fun every day.

With that, I'm committing to #100DaysOfCode! Starting tomorrow I'll post about what I code each day.