In the TV show The Bear, there’s a scene that shows a wall with a timer and a plaque beneath it. The plaque reads: “Every second counts.”

Sometimes clarity doesn’t arrive all at once—it shows up later, disguised as advice you didn’t know you were writing. This is about one of those moments.

It doesn't matter if it's good right now. It just needs to exist.

Feeling overwhelmed? Write it down. Feeling lost? Write it down. Feeling inspired? Write. It. Down.

Use a pen, not a pencil. Make a mistake? Scratch it out. Live with it. Move on.

Yesterday, after publishing a new blog post—the first one in about two years—I had a realization. I’ve become really good at writing. But I’ve stayed really bad at sharing.

For over a year, I logged every 30-minute chunk I could’ve spent making my life—or someone else’s—better. Every half hour where I gave into impulse and gave up control… was no longer mine.

I woke up at 5:00 AM today, not as part of a "seize the day" productivity practice, but because I struggled to fall and stay asleep. Like many of us, I grabbed my phone and spent 30 minutes scrolling through it, a decision I knew I would regret.

This is the story of how I learned how to code. In short, how I learned was by (no lie) reading through the entire source code of jQuery. I did this about 10 years ago.

Before working in the tech sector, I spent several years working in restaurants. There were many things I learned from my time on the line.

Sometimes, the most productive thing you can do is to detach from the digital and return to the simplicity that is analog. There's profoundness in the level of productivity you can experience with some things so primitive.

Working with globalized variables maybe one of the trickier aspects to any design or code project. It’s sort of like accumulating a collection of a particular collectable, say Pokemon cards. It’s cool that you can collect these cards! I mean, who wouldn’t want an original 1st edition base set Charizard.

One of the more “abstract” but important and powerful systems within G2 Components is it’s “Context” system. Given the name, those familiar with libraries like React may immediately think of React.Context. It’s kinda close, but it’s much much more than that.

One of the biggest and most important challenges for the G2 Components project was defining and creating the Style system. The Style system is one of the core system that’s responsible for managing and powering the entire UI layer for the library.

In other words… smoothly transitioning from one thing to another thing! In traditional animation (think the good ol’ hand drawn stuff), this process of transitioning between two key poses (or key frames) is known as inbetweening.