When 25 minutes was a luxury
I was about nine months into parental leave when my manager emailed to say my role would shift toward reporting when I came back. Translation: I needed to learn SQL, and I had roughly twelve weeks to do it.
The catch was time. Days were for the baby. By the time dinner, bath, and bedtime were done, it was 10 p.m. at the earliest. Still, I was motivated. I opened my laptop, set the timer for 25 minutes, and pressed Start. Around minute twelve, the baby monitor crackled. By the time I got him back down, half an hour had gone by. Same thing the next night. And the night after that. Three nights, zero finished sessions.
What went through my head was something like, 'Okay, the Pomodoro thing is for people who actually have uninterrupted time.' I'll admit I felt a little sorry for myself.
"Fifteen beats zero"
On the fourth night, my partner caught me sighing at the laptop. "Are you still doing this tonight?" "I have to. He's just going to wake up again, though." "So don't do 25. Do something shorter." "What am I supposed to learn in 15 minutes?" "More than you learn in zero."
My first thought was, 'That's annoyingly hard to argue with.' So I didn't. I went into the timer settings and changed focus to 15 minutes and the short break to 3.
It stung a bit. Everyone online talks about 25- or 50-minute blocks, and here I was at 15. But when that first alarm went off, something shifted. For the first time all week, I had actually finished something. All I'd done was work through five SELECT examples, and it still felt like a win.
What changed at 15 minutes
Fifteen minutes was short enough that I stopped gambling on it. With 25, I'd sit there guessing how long I had before he woke up. With 15, I just hit Start. Starting got easier, so I sat down more often.
The three-minute breaks were mostly for glancing at the baby monitor, grabbing some water, and going again. The first week I averaged three sessions a night. By week two it was four or five. That adds up to barely an hour, but the week before I'd done basically nothing, so it felt huge.
For sound, I ran quiet rain in one earbud and left the other ear open on purpose so I could still hear the baby. The rain covered the fridge hum and street noise, which helped me. That's just what worked in my house, though.
Rules for the nights he woke up
Even at 15 minutes, some nights he woke up anyway. At first I'd hit Pause, run to his room, then come back and resume. But after twenty minutes of rocking a baby, resuming the last seven minutes of a session got me nowhere. I'd stare at the screen thinking, 'Wait, what was this query supposed to do?'
So I made a rule. Back within ten minutes? Resume. Longer than that? Reset and start the session over. And right before hitting Pause, I'd jot one line in a notebook, something like "writing JOIN, customer table on the left." That one line saved me so much flailing when I came back.
One night I got him back down around 1 a.m. My partner was waiting in the hallway. "Come to bed. Do it tomorrow." "Just one session." "Because it's only 15 minutes?" "Exactly." My partner laughed and went to bed, and I finished that session before following. If it had been 25 minutes, I would have closed the laptop.
I stopped counting the nights I missed
Plenty of nights went nowhere: a sick kid, or me running on empty. Early on I marked those days with a big X on a wall calendar. By week two the calendar was mostly X's, and looking at it just made me want to quit. So I took it down.
After that, I only circled the days I studied and wrote the session count inside. When the "Are you still doing this tonight?" question came and my honest answer was "Not tonight," I took the night off without guilt. Weirdly, the day after a guilt-free night off was often one of my better ones.
To be clear, I'm not saying 15 minutes is the right length for everyone. In my situation, 25 minutes wasn't survivable, and shortening it is what made the whole thing work. Twenty-five is a starting point, not a rule. I just had to learn that the hard way.
Three months later
Over those three months I circled 55 days and logged around 140 sessions, roughly 35 hours. That won't make anyone an expert. But in my first week back, when my manager asked, "How's your SQL?" I could say, "I've got the basics," and mean it.
At work I'm back to 25-minute sessions now, and I had no idea how long and peaceful 25 uninterrupted minutes could feel. If your time comes in short, unpredictable scraps like mine did, here's what I'd pass along.
- If 25 minutes keeps getting cut off, drop to 15 or even 10. Finishing a session matters more at first.
- Before you hit Pause, write down what you were in the middle of. One line is enough.
- Back within ten minutes, resume. Gone longer, reset and start fresh.
- If you need to hear your kid, keep background sound low and in one ear only.
- Track the days you did something, not the days you didn't. Rest nights are allowed.
- When life opens up, lengthen the timer again. The short version is a way to get through a season.