
Last winter, a systems engineer, whom I will simply call “the colleague down the hall”, set three goals for the working year: earn a respected credential by spring, spend almost nothing doing it, and come out able to build real things. By April the engineer was exhausted, over budget on evenings and still unsure what had actually been learned. Nothing was wrong with that discipline. The real problem was asking one plan to be fast, cheap and good all at once. This article turns that experience into a checklist you can run through before you commit your year, so you choose which corner to give up deliberately.
Why a checklist, and why now
Career decisions in DevOps tend to be made in a rush. A job posting mentions a skill, a friend passes an exam, a conference talk sparks enthusiasm, and suddenly an ambitious plan appears. A written checklist slows that moment down by about fifteen minutes, which is usually all it takes to notice the plan is demanding more than three corners can give.
Work through the sections in order. Write short answers, even if only to yourself.
Section one: define your three corners in your own words
- Fast. What is the real date by which this needs to be done? Is it driven by a job, a contract or only by impatience?
- Cheap. What is the most you are willing to spend in money, and how many evening hours per week can you spare without damaging sleep or relationships?
- Good. What would “good” look like in six months: a certificate on file, a project you can demonstrate, or confidence in an interview?
The point is to stop using the words loosely. “Good” in particular hides several meanings, and the checklist works better when you pick one.
Section two: rank them honestly
- Which of the three could you sacrifice for the next three months with the least regret?
- Which one would you refuse to sacrifice even if the plan collapsed around it?
- Does anyone else, such as an employer or family, hold a stake in your answer?
Our colleague down the hall realised that “cheap” mattered less than assumed. The employer would have covered a structured course, but nobody had asked. The plan had been guarding a corner that was already protected.
Section three: look at where careers typically stall
Career paths in this field rarely run in a straight line. A guide to the route from junior engineer up to a senior DevOps position shows that time in role, breadth of experience and visible results all contribute, and none of them can be rushed cheaply. Another perspective is offered by an article on new routes into DevOps for working developers, which makes the point that different starting points favour different trade-offs. A developer already comfortable with code can often move quickly into automation, whereas someone from a support background may need more time.
Section four: pick a plan shape
Match your ranking to one of three shapes.
- Fast and good, and money flows. Look for sponsored training, a mentor at work or a paid lab environment. Expect to spend.
- Cheap and good, and time flows. Build projects at home at a steady pace. Expect the plan to run through the year.
- Fast and cheap, and depth gives. Aim for a narrow, well-defined result, such as passing a single exam, and plan to deepen later.
Circle one. If you are tempted to circle two, go back to section two.
Section five: protect the plan from creep
- Write the chosen trade-off on a card and keep it visible near your desk.
- Decide what you will say no to this month: a second certificate, an extra side project, a new tool.
- Pick one checkpoint per month to ask if the plan still matches your ranking.
- If your circumstances change, such as a new job or a family event, rerun sections one to four rather than patching the old plan.
A short aside on where to read more
Wanting a quick, jargon-light read on operations costs, our colleague came across cloudopsnow.in, titled as a CloudOps blog, which keeps its entries brief. It was never treated as a syllabus. It simply supplied a few plain sentences about cloud spending that could be repeated to a manager when the budget question came up.
Section six: the human side
Checklists miss the emotional part, so here are questions no template can answer for you.
- When did you last feel energised by learning, and what were you doing?
- Will you resent the sacrificed corner in three months?
- Who can you tell about your decision so that you stay accountable?
The colleague down the hall now describes the second attempt differently. Depth and low cost came first, speed was given up, and the manager was told that the credential would arrive in autumn instead of spring. The plan took longer, but energy was left over for the rest of life, and the project built along the way came up in the next performance review.
Worked example: filling in the checklist
To see the checklist in motion, imagine an engineer with a full-time job, a modest learning budget and a goal of moving into platform work within a year. In section one, “fast” is defined as twelve months, “cheap” as a fixed amount for exam fees and a lab subscription plus five evening hours a week, and “good” as a working project that can be demonstrated in interviews. In section two, the engineer realises that the project matters more than the certificate, so the credential is the corner that can wait. Section four then points to the cheap-and-good shape: steady evenings, a small set of linked projects and a single exam booked late in the year.
Sections five and six add guardrails: a card on the desk reading “project first, exam last”, a monthly check on the first Sunday, and a conversation with a partner about weekend hours. None of this is sophisticated. Its value is that every future decision, such as whether to take on a second course in March, can be measured against a choice that was made calmly rather than reactively.
What if two corners truly cannot give?
Sometimes a person honestly cannot relax any corner, for instance when a job offer depends on a credential by a fixed date and quality cannot be skipped. In that case the checklist still helps, because it shows where the missing resource must come from. Usually it is money, for guided help, or someone else’s time, for a mentor at work. If neither is available, the honest conclusion is that the plan as stated is not feasible, and the date or the scope needs to change. Hearing that on day one is kinder than discovering it in week twelve.
Using the checklist with a team
Managers can run the same exercise in a one-to-one. Ask the person which corner they would give up, listen without offering a fix, and write down what they say. Often the answer is a surprise, such as a person who would happily spend weekends to move faster, or one who needs a slower pace because of caring duties. Recording the choice makes later conversations easier, because progress is judged against the plan the person actually chose, not against an imagined plan that nobody agreed to.
Final step: date it and move on
Finish by writing today’s date next to your answers. In three months, read them again. If the trade still fits, carry on. If not, change it on purpose, and note why. A plan that is revised openly is a sign of good judgment, not failure. The aim of this checklist is not to guarantee a perfect year, but to make sure that whichever corner gives, you chose it yourself.