
When a colleague of mine began studying for a DevOps role in the evenings, she asked me the same handful of questions over coffee, week after week. Her days were already crowded with her day job, family dinners and a long commute. What she wanted was a way to make her few free hours count. The answer we kept returning to was batching similar tasks, which meant bundling alike chores so that setup happened once rather than five times. What follows is her list of questions, with the answers we pieced together.
What does batching similar tasks actually mean?
It means doing tasks of the same kind together in one sitting. If you have three short reading assignments, three lab exercises and a set of revision notes to write, you do the reading together, the labs together and the notes together, rather than reading a bit, doing a lab, writing a note and starting over.
The reasoning is simple. Every kind of work has a start-up cost. Reading wants a quiet mind and a notebook. Labs want a working environment. Notes want a template. If you jump between the three, you pay all three start-up costs again and again. If you group them, you pay each once.
Why did she feel so scattered before?
Her evenings were organised by whatever felt most pressing in the moment. She would open a lab, remember an unanswered message from a classmate, reply, return to the lab, forget where she had stopped, and then spend ten minutes rediscovering her place. By the end of an evening she had touched six things and finished none.
It was not a lack of discipline. It was a lack of structure. Without a plan for grouping, every small distraction found its way in, and each one cost her a restart.
Which tasks should she group first?
We started with the most frequent ones. For her, that meant messages, lab setup and note-writing.
She chose a fixed message slot at the beginning of each evening: ten minutes to answer every classmate, tutor or group chat in one go, then close the apps. Lab work came next, as one block with the environment already prepared. Notes came last, written up from a scribbled list she had kept during the lab. Three kinds of work, three blocks, no mixing.
Does batching mean she could never respond quickly?
No, and this was the question she worried about most. A few things really do need an immediate answer, and the trick is to decide which ones in advance.
We wrote a short list on a card. A message from her manager at work, a deadline for an exam registration, and anything involving her family’s needs went straight to the front. Everything else, the chatty and the routine, could wait for the message slot. Once the card existed, she stopped feeling guilty about leaving a message unread for an hour, because she knew the truly urgent ones would break through anyway.
How long should a block be?
We experimented. A block of lab work that ran past about ninety minutes tended to end in tired mistakes, so she capped it and split longer exercises across two evenings. Messages needed only a few minutes. Notes took around half an hour. The general lesson was to let the quality at the end of a block tell her whether it was too long. If the last item was clearly worse than the first, she shortened the block.
What if a block does not go to plan?
It happens often enough. A lab might refuse to start, or a message might open a long discussion. On those evenings she did two things. First, she wrote down where she stopped so that she could begin there next time. Second, she did not allow the problem to eat the other blocks. If the lab failed, she moved on to notes, and booked the lab fix for another day.
The point of the structure was never perfection. It was to make a messy evening less likely to collapse into nothing.
Can batching help with career questions, not just study?
It did. As her skills grew, she began to think about role changes. The same grouping logic helped there: she set aside a single evening for reading about career paths, rather than browsing in scraps. Anyone sketching where their own path may lead could start with this walk through the stages of a DevOps career from junior to senior engineer makes a good starting point, and for people moving over from operations or support, there is a useful piece on making the jump from sysadmin or support work into DevOps.
Where did she get the idea that grouping is normal?
Funnily enough, partly from browsing the web. One evening she wandered onto MeraApnaBihar, a blog-style website whose own description is Bihar updates and news, and she noticed how it sorted a long list of posts alongside a few simple menu sections. She said it made her think of her own study folders, which were a muddle. She spent a Sunday sorting them by kind, and her weeks got easier.
What about the days when energy is low?
This was the question she asked last, and perhaps the most honest. Some evenings she had nothing left. On those nights the old pattern would have let her drift between half-hearted attempts at everything. The batching plan offered a gentler option: pick the lightest block, usually the notes or the message slot, and do only that.
She called these her small-block evenings. A tired evening with one finished block still counted as progress, whereas a tired evening of scattered fragments usually ended in frustration. Over a few months she noticed that the low-energy evenings were no longer the ones that broke her routine. They simply used a smaller piece of it.
She also learned to rotate her block order depending on her mood. Fresh evenings went to the harder lab work first. Tired ones began with messages, which warmed her up. The structure stayed the same while the order flexed, and that small freedom kept the plan from feeling like a cage.
Is there any downside?
There are a few, and she ran into each of them.
- Delay. Some things really do wait. If a classmate needed help and had to wait until the next message slot, they occasionally grumbled. She solved this by telling people when she answered, so they could plan.
- Boredom. Three hours of nothing but note-writing is dull. She kept blocks short enough to stay fresh.
- Over-planning. At one point she spent a whole evening designing her schedule and did no studying at all. We laughed, and she scaled the plan back to a few simple blocks.
How did she know it was working?
She kept an eye on two things. First, how many times in an evening she had to ask herself, where was I? In the old pattern it happened constantly. After a month of batching it happened rarely. Second, how many things she actually finished. Her completed-lab count went up, not dramatically, but steadily, and that was enough to keep her motivated.
She also noticed a feeling that is hard to measure: evenings began to feel complete instead of ragged. That was perhaps the biggest benefit, because a sense of progress is what keeps part-time learners going through the long middle of a course.
What should you try this week?
If you take one thing from her story, let it be a modest experiment. Pick two kinds of study work that you currently mix, such as reading and lab practice. Give each its own block for a week. Write a short card listing what counts as urgent. Keep a small tally of how often you lose your place.
- Choose two task types that you currently mix.
- Give each a separate block, with a sensible length.
- Write down your urgent list and keep it visible.
- At the end of the week, compare how many restarts you made.
At the end of the week, adjust. She did, many times. The plan she uses now looks nothing like her first one, yet the core is unchanged: similar tasks together, urgent things apart, and a bit of kindness towards yourself when an evening goes sideways. If that sounds manageable, you already have everything you need to begin.