{"id":1972,"date":"2026-11-11T00:50:00","date_gmt":"2026-11-11T00:50:00","guid":{"rendered":"https:\/\/devopsschool.org\/blog\/?p=1972"},"modified":"2026-11-11T00:50:00","modified_gmt":"2026-11-11T00:50:00","slug":"marathon-vs-drill","status":"publish","type":"post","link":"https:\/\/devopsschool.org\/blog\/marathon-vs-drill\/","title":{"rendered":"Marathon Sessions vs Short Drills: Which Builds DevOps Skill?"},"content":{"rendered":"

Two engineers start learning the same infrastructure tool on the same Monday. One blocks out three hours every Saturday and works through whatever feels interesting. The other spends fifteen minutes, three evenings a week, on the single step she finds hardest. After three months, who is better? Plenty of people assume the Saturday marathon wins on sheer hours. In practice, the evening drills often pull ahead, and the reason comes down to how deliberate practice<\/strong> differs from long unfocused sessions. Below, the two styles go head to head on five measures, and you can pick your own blend afterwards.<\/p>\n

The contenders<\/h2>\n

The marathon.<\/strong> A long block of study or lab time with a loose goal, such as “get comfortable with infrastructure code”. Content is chosen as you go. Feedback arrives mostly when something breaks.<\/p>\n

The drill.<\/strong> A short, timed exercise aimed at one named weakness, such as “write a module whose variables are validated before apply”. It has a pass mark, quick feedback and exactly one adjustment between attempts.<\/p>\n

Neither is wrong. They do different jobs, which becomes clearer when we compare them on a few dimensions.<\/p>\n

Round one: attention<\/h2>\n

Marathons tend to start sharp and fade. By the second hour most people are skimming, copying commands without thinking or checking messages. The result is a pile of hours in which only the first forty minutes carried real learning.<\/p>\n

Drills stay short enough that full attention is realistic. Fifteen minutes with the phone away is easy to defend. Edge: drill.<\/strong><\/p>\n

Round two: breadth<\/h2>\n

Here the marathon shines. A long session lets you wander, connect ideas and see how pieces fit. If you are meeting a new area for the first time, you need that exploration, because you cannot drill a weakness you have not yet encountered.<\/p>\n

Drills are narrow by design. Used alone, they can leave gaps in your map of the field. Edge: marathon.<\/strong><\/p>\n

Round three: feedback<\/h2>\n

In a marathon, feedback is often accidental: an error message, a failed build, a colleague’s passing remark. Valuable, but irregular, and easy to miss when you are in flow. A drill builds the check into the exercise. You decide the pass mark beforehand, measure the result and often ask one reviewer a narrow question. Honest, quick feedback is the single biggest reason drills improve skill faster. Edge: drill, clearly.<\/strong><\/p>\n

Round four: transfer to real work<\/h2>\n

This one is closer. A marathon that mimics a real project transfers well, since the whole workflow is practised. A drill transfers only if the fragment you drilled actually shows up at work. Choose the target from real friction, such as the step you ask others about or the task that always overruns, and the transfer is excellent. Choose an arbitrary target and it is nil. Edge: even, depending on target selection.<\/strong><\/p>\n

Round five: motivation and sustainability<\/h2>\n

Long blocks are hard to schedule and easy to skip. One cancelled Saturday can become three. Short drills fit in the gap before dinner and survive a hectic week. They also give you small, visible wins, because the time on a repeated task falls where you can watch it. On the other hand, some people enjoy the immersion of a long session and find short drills dry. Edge: drill for consistency, marathon for enjoyment.<\/strong><\/p>\n

If you want something to compare your habits against, a blog piece on building the habit of reasoning through DevOps problems<\/a> offers a lens on what skill actually looks like in the job, which helps you decide what to drill.<\/p>\n

Two learners, three months later<\/h2>\n

Return to our two engineers. The Saturday learner ended the quarter with a long list of things she had seen and a few she could do fluently, mostly the ones she had met by accident several times. Her biggest gain was confidence about the vocabulary. When a real task arrived, though, she still reached for notes on the same two steps.<\/p>\n

The evening learner had touched fewer topics. But the step she had drilled, validating inputs before applying changes, took her four minutes where it once took twenty, and she could explain it to a colleague without hesitation. Her notes file showed twelve small adjustments across six weeks, each recorded with a result. When asked what she had improved, she could answer with evidence rather than a feeling.<\/p>\n

Neither outcome is a verdict on talent. They show what each style produces. One produced familiarity across a wide area, the other produced fluency at a narrow point. The best engineers tend to have both, built in sequence: a broad pass, then focused repair of what the pass exposed.<\/p>\n

Common traps in each style<\/h2>\n

The marathon’s trap is mistaking activity for progress. You finish a Saturday tired and satisfied, yet unable to say what is different about your abilities. The cure is to end every long session by writing the three moments you got stuck.<\/p>\n

The drill’s trap is polishing strengths because they feel good, and over-narrowing until you can do one thing perfectly in a sandbox and nothing else on the job. The cure is to choose targets from real friction and to apply each improved step to live work within a week.<\/p>\n

Scoreboard<\/h2>\n