Dev Velocity Lab
← Back to blog
engineer-growth

I Read Atomic Habits Twice. The Second Time, I Actually Changed Something

I've read five or six productivity and learning books in a row, and the one that stuck was the one I'd already read. Here's the 15-to-30-minute daily learning habit I built from it, and why I think it matters more than any single book.

Watch on YouTube
ShareX / TwitterLinkedIn

I just started Atomic Habits for the second time, and it's hitting much harder than it did the first time. I'd just finished five or six other books on productivity and learning, and this is the one that stuck. The core idea is simple, and I think that's why it's easy to nod along to and hard to actually do.

The compounding part is the whole point

Repeated habits compound in both directions. A good habit makes you a little better each week. A bad one makes you a little worse, and you don't notice until you're well behind where you started.

I realized I'd been doing the second thing without noticing. When I wasn't deliberately learning, I was scrolling, or sitting in my head overthinking, worrying, or daydreaming about things I hadn't achieved yet. I wasn't making a conscious choice to fall behind. I just wasn't making a conscious choice to move forward, and that's enough to slide.

If you don't intentionally point yourself somewhere, the default is neutral at best and negative over time.

What I actually changed

I didn't overhaul my life. I just stopped wasting the time I was already spending:

  • Audiobooks during my commute and chores. This is the one that's working. I'm learning while I do dishes and drive, time that used to go to my phone.
  • 15 to 30 minutes of intentional learning per day. Small enough that I don't skip it, real enough that it adds up.
  • Smaller habits stacked on top. Writing down my goals and talking to myself more positively. Each one is tiny, but they reinforce each other.
  • Hands-on learning. Building projects and learning how to work with agents, not just reading about them.

Over the past couple of weeks I can already see the difference. Nothing dramatic happened. I just started to notice more clearly what I was learning and less of the spiraling.

If you're new to a stack or a role

If you've been moved onto a stack you didn't pick and you feel behind, this is what I'd try:

  1. Pick a fixed daily slot. Attach it to something you already do, like commuting, a walk, or lunch. Don't rely on motivation.
  2. Keep it to 15 to 30 minutes. You want to be able to show up on bad days too.
  3. Learn by building. Reading alone won't get you fluent. Make one small, real thing each week in the unfamiliar tech.
  4. Replace the spiral, don't just add to your day. When you catch yourself overthinking or doomscrolling, do the learning block instead. That's where most of the time comes from.
  5. Track it loosely. A note of what you learned each day is enough to see the compounding.

The honest part

This is simple, common-sense stuff, and it's still hard to make a daily practice. I don't have it perfectly figured out. I'm just documenting what's helping me now and how I'm tweaking it. I plan to keep sharing both the technical and non-technical side of this, including what works, what doesn't, and what I change.

If you're trying something similar, I'd like to hear what your 15 minutes look like.