I wanted to learn System Design. I had the course, the material, and a clear list of what to cover. So I started. Some days I got through two topics. Some days one. Some days nothing.

A month in, I had no idea where I actually stood.

Not because I wasn't trying. Because I had no honest way to see my progress. No clear picture of what I'd covered, what was left, or whether I'd actually been showing up at all.

Start Ember is a habit tracker I built to fix this for myself. The idea was simple: show up every day, build a streak, make the work visible. It worked well for daily habits. Then I tried to use it for learning, and ran into a different problem entirely.

Two Different Types of Work

The habit model works perfectly for things like drawing, meditating, or reading. Things you want to do forever. There's no finish line, only whether you showed up.

Learning System Design is different. It has a beginning and an end. There's a body of material you're moving through. Marking "System Design" every day tells you nothing useful. It doesn't tell you whether you're actually getting through the content, or whether you've been circling the same two topics for three weeks.

Halfway through, I realized I'd been doing exactly that. I had "System Design" as a daily habit in Start Ember, felt like I was showing up, and still couldn't tell you what I'd actually covered. The habit model was giving me the feeling of progress without the substance of it.

A curriculum isn't a habit. Treating it like one is where progress quietly dies.

What Habits and Tracks Actually Do Differently

A habit is about identity. You're not trying to finish drawing, you're becoming someone who draws every day. The streak isn't about the output. It's about who you are on day 30 versus day 1.

A learning track is about movement through material. There's something in front of you, a course, a book, a roadmap, and you're moving through it. The question isn't "did I show up today?" It's "where am I in this thing, and am I actually moving forward?"

Both modes matter. Mixing them up is where most people quietly lose momentum, myself included.

What Tracks Are

A Track is a named curriculum you're working through.

You give it a name ("System Design"), a source ("AlgoMaster Low-Level Design"), and a list of checkpoints: the topics, chapters, or modules you'll cover. Then you work through them one by one, marking each done when you've genuinely covered it.

The view is honest and minimal:

8 of 24 checkpoints completed. Shows where you stand.

Last activity: 12 days ago. This is the line that matters. If you haven't touched a track in almost two weeks, that number sits there quietly and tells you the truth.

The Habit Connection

Some checkpoints aren't one-time topics. They're things you want to build a daily practice around. "Solve system design problems daily" might be a stage in your learning track, but it's also something you want to show up for every single day.

In Start Ember, you can link a checkpoint directly to a habit. The checkpoint marks where you are in the material. The habit tracks whether you're showing up for the daily work that stage requires.

The track is how you move through the curriculum. The habit is how you make it stick.

Start Simple

You don't need a complicated system. Pick something you're learning from a specific source, break it into chunks, work through the chunks. When it's done, it's done.

Start Ember holds that clearly, shows you where you stand, and tells you the truth about whether you've been showing up.

Start Ember is a free habit and learning tracker. Try it at start-ember.vercel.app

If this resonated, or if you've been quietly misusing your habit tracker the same way I was, drop a comment below.