
Imagine two people starting a DevOps career in the same month. Mila says yes to every tutorial, every certificate offer and every group chat invitation. Daan keeps a small card in his wallet with six lines on it, all beginning with the word “not”. Eighteen months later Daan is shipping real changes at work and Mila is still collecting course completions. The difference is not talent or hours. It is that Daan decided early what he would ignore. This explainer describes that idea in everyday terms and shows how a beginner can use it without any special equipment.
The idea in one sentence
Your attention is limited, so write down what you will not give it to. That is all a “not-to-do list” is. A normal to-do list grows because adding is easy and removing feels like failure. A not-to-do list works in the other direction. It names things that tempt you, so the few that matter get your full effort.
Why DevOps beginners need it more than most
The field touches servers, code, networks, security, automation and teamwork. Every one of those has a stack of tools, and every tool has a fan club. A beginner scrolling a job board sees dozens of unfamiliar names and concludes that all of them must be learned. They cannot be. Even experienced engineers know a handful well and the rest only by reputation.
If you are still working out where you are headed, a map of the stages helps. This outline of the road from a junior position to a senior one shows that each stage asks for a few particular strengths, not everything at once. Knowing the stage you are in tells you what can wait.
Daan’s six lines
The card in Daan’s wallet read roughly like this:
- I will not learn a second scripting language until I can use the first without looking things up.
- I will not start a new course before I finish the one I am on.
- I will not read opinion fights about which tool is best.
- I will not answer chat messages while I am practising.
- I will not collect certificates that no employer I want has mentioned.
- I will not compare myself with people who have worked ten years longer.
Notice what is missing: nothing on the card says Daan is lazy or uncurious. Each line protects a particular piece of effort. The sixth is about feelings, not tasks, and it ended up carrying real weight.
What goes on the card, in plain words
You do not need cleverness to build yours. Think of four boxes:
- Things to read. Which newsletters, feeds and threads will you leave unopened?
- Things to learn. Which tools or languages are not for this year?
- Things to join. Which groups, calls and channels will you step out of?
- Things to answer. Which messages and requests can wait, or be declined?
Two or three lines per box is plenty. Keep sentences short enough to remember without looking. If a line needs a paragraph to explain, split it or drop it.
A note about certificates
Certificates are a common trap because they look like proof of progress. Some are valuable, and some are simply popular. Before adding one to your plan, ask what role it points toward and whether a hiring team you respect asks for it. Reading about the skills involved is a gentler way to decide than buying an exam voucher. For example, a guide to DevOps certifications arranged from beginner to advanced can help you see which ones sit well beyond your current stage, and so can be skipped without worry.
How Daan learned to keep the list honest
He did not follow the card perfectly. Some weeks he broke three lines before lunch. What mattered was that he noticed. On Sunday evenings he checked the card and asked two questions: which line did I break, and did it cost me anything? If the answer to the second question was “no”, he considered removing the line. If it was “yes”, he kept it and moved it higher.
He also allowed one weekly slot for wandering, a couple of hours when he could read or watch whatever he liked. That small outlet made the refusals during the week much easier. Curiosity needs somewhere to go.
Where the list meets your growth plan
A skip list on its own does nothing; it needs something to protect. Pair it with a modest plan for the skills you do want. A written roadmap of skills, projects and certifications for a DevOps engineer gives you a menu from which to pick two or three items per quarter. Everything not picked is a candidate for the card.
Ordinary decisions work the same way
Daan used the idea outside work too. When he needed a new keyboard and a note-taking app, he opened a review blog, True Review Now, a site where people read about gadgets, software and local services before buying, and wrote down beforehand which features he did not care about. The shopping took an evening instead of a week.
Common questions from beginners
Will I miss something important? Occasionally, yes. But important things tend to reach you through colleagues and projects anyway, and the cost of missing a trend is usually smaller than the cost of never finishing anything.
How long should the list be? Short enough to fit on a card. Six lines worked for Daan; four may suit you better.
When do I change it? Whenever your situation changes: a new job, a new project, a new goal. The card is a tool, not a vow.
Start with one line
You do not need to build the whole thing tonight. Write a single sentence that begins “I will not” and tie it to something you are currently tempted by. Put it where you will see it tomorrow morning. If it helps, you have begun. If it does not, rewrite it. Either way you will learn something about where your attention was going, which is a useful thing to know at any stage of a career.