Skip to content

Prepare First or Dive In? Two Ways to Start a DevOps Task

Published November 21, 2026 by Beena Yadav

There are two kinds of engineers at the start of a task. One opens the editor and begins typing, fixing problems as they appear. The other pauses for a short while to get the surroundings in order, and only then begins. Both mean well, and both have stories to tell. Here the two approaches sit next to each other, seen from the perspective of someone building a DevOps career, and borrows the term cooks use for the second approach: mise en place, everything in its place before the work starts.

The diver: start now, tidy later

The dive-in style has real charm. It feels productive. You see output within minutes, and early momentum is a good teacher. Many people learned their first scripts this way, and for throwaway experiments it is perfectly reasonable.

The trouble appears when the task grows. Halfway through, the diver needs a test account that does not exist, a log that was never turned on, or a copy of the data from before the change. Each gap interrupts the flow, and each interruption is small enough to feel normal. At the end of the day the work is done, though it stretched past what it needed, and the missing hours are hard to trace.

The preparer: a quiet start, a steady middle

The preparer begins more slowly. The first ten minutes look unproductive to an observer: a branch is created, the environment is checked, notes are opened, a sample of the data is set aside. Then the work begins, and it tends to flow. There are fewer pauses, fewer questions to colleagues and a clear way back if something misbehaves.

The weakness of this style is that it can become a ritual with no end. Some people prepare until the preparation is the work. The remedy is a time limit and a short list, which keeps the setup useful rather than decorative.

A side-by-side look

  • First ten minutes: the diver produces visible output; the preparer produces a ready environment.
  • Middle of the task: the diver stops to look things up and request access; the preparer rarely stops.
  • When something breaks: the diver searches for the last good state; the preparer opens the rollback note.
  • At handover: the diver reconstructs what happened from memory; the preparer points to notes and a baseline.
  • Stress level: the diver feels it rise as gaps appear; the preparer feels it stay flat.

Neither column is moral. They are two different ways of spending the same hours, and the right choice depends on the task. A quick, reversible experiment on a disposable machine favours the diver. A change to anything shared, anything customers touch or anything others will have to maintain favours the preparer.

What it means for a career

Early in a DevOps career, the diving habit is common and forgivable. People who grow into senior roles, however, tend to be recognised for something else: they make work predictable for others. A teammate who sets out the environment, records the inputs and writes the way back is easy to hand work to and easy to hand work from. Career guides such as this outline of the climb from junior engineer to senior DevOps practitioner describe growing responsibility, and preparation is one of the quiet ways that responsibility shows up in daily work.

The same applies when you are planning your own growth. A roadmap, like the one in a roadmap for DevOps engineers spanning skills, projects, certifications and growth, is easier to follow if each project begins with a tidy setup, since the portfolio pieces that result are easier to explain, repeat and show to an interviewer.

A story from the middle

Consider an engineer who had always dived in and was asked to update a build pipeline for a shared service. The first attempt, in the old style, broke the nightly build for two teams because a cached credential had expired and nobody had checked. The second attempt, a month later, began with a different ritual. The engineer copied the pipeline into a scratch project, confirmed that the credentials worked, saved the old configuration beside the new one and told the two teams when the change window would open. No drama followed, and that was the whole idea. Colleagues did not notice the change at all, and the engineer quietly earned a reputation that few shortcuts can buy.

Learning from places that prepare by trade

Looking beyond software helps keep the habit fresh. People who stage concerts, workshops and festivals live by preparation: schedules, access, signage and spares are arranged before anyone arrives. MumbaiOrbit, an events website for Mumbai, brings together what is on, where it happens, forum chatter and blog posts, and it shows how much structure supports a place where people simply want to find something to do. Engineers can borrow that outlook in small ways, such as keeping a printed or pinned checklist next to the screen.

How to choose between the two

  1. Check whether other people rely on what you are changing; if they do, prepare.
  2. Check whether you could undo it within a minute; if you could not, prepare.
  3. Check whether you will need to explain it afterwards; if so, prepare.
  4. When none of the three applies, dive in, but still keep notes.

Most professional work lands in the first three categories, which is why the preparer’s habit tends to win over a career. Even so, the divers have something to teach: their willingness to start prevents endless planning, and a good engineer keeps a little of both. Set the bench in ten minutes, then move with confidence.