
Most DevOps careers are steered by assumptions nobody has checked. “I need another certificate.” “I should be on every platform.” “Posting more will get me noticed.” A quarterly start-stop-continue retrospective is a blunt, cheap way to test those beliefs against what actually happened in the last three months. This post takes five common career myths and shows how the three lists knock each one down. No theory, just what to write and why.
The start-stop-continue retrospective in thirty seconds
At the end of a quarter, look at your work, learning and visibility. Write three lists. Start: things you are not doing that would help. Stop: things you are doing that cost more than they give. Continue: things that clearly worked. Keep two or three items per list. Tie each to something you can check in three months. Nothing more is required, and it is enough to expose the myths below.
Myth one: “More certificates mean faster progress”
Certificates have a place, but they are not a speed dial. Look back over the quarter and ask what actually changed your day-to-day value: the course you finished or the incident you helped resolve? Many engineers find that one hands-on project taught them more than a stack of exam preparation. If that is true for you, the lists say it plainly: start building and documenting a small project each quarter, stop collecting credentials without a use for them, continue the one learning habit that produced real skill.
Do not take this as a rule against certification. If a credential opens a door you need opened, put it on the start list with a reason and a date. The retrospective only asks that every learning item has a purpose you can name.
Myth two: “I have to learn every tool”
The tooling landscape grows every month, and the fear of falling behind is real. But a quarterly look back usually shows a pattern: a small set of tools did most of the work, and the rest consumed hours for little return. Write down the tools you actually used in anger. Those are the ones to deepen. The stop list is the place for the shiny tool you tried for a week and abandoned.
A practical example: someone who spent weeks tinkering with several container topics might find that their daily value came from a clear grasp of image hygiene and a few common beginner traps. A guide such as a rundown of the usual beginner slip-ups with Docker is a typical resource for a start item, because it covers the fundamentals that pay off every day. Depth in fundamentals beats breadth in trends.
Myth three: “Personal branding means posting constantly”
Visibility matters for independent careers, but more output is not the same as more impact. In your quarterly review, count the posts, talks or contributions you made and note which ones led to anything: a conversation, an invitation, a request for help. You will probably find that a small share of your output produced most of the results.
- Start: write fewer, more specific pieces based on problems you solved this quarter.
- Stop: stop posting on a schedule if the posts are filler.
- Continue: keep answering questions in the places where people already look for help.
That pattern, fewer and better, appears often. The review gives you the evidence to commit to it without guilt.
Myth four: “A retro is only for teams”
A career is a project with one team member, and it deserves a review as much as a release. The solo version needs a page, a quiet half-hour and honest answers. If you work with a mentor or a trusted peer, show them the lists. A second reader catches wishful thinking, such as a start list full of items that need twenty hours a week you do not have.
For a related example of the kind of structured learning content a DevOps person can build a start list from, see a piece on Docker’s role in automated CI/CD delivery. Notice how a focused topic gives you a concrete project rather than a vague ambition.
Myth five: “If it feels productive, it is working”
This myth is the most persistent. Busyness feels like progress. Checking dashboards, reading threads and tidying notes all feel productive. The retrospective forces a harder question: what did this activity produce? An hour that produced a working script, a finished lesson or a repaired relationship counts. An hour that produced a feeling of being informed may not.
Move the suspicious activities onto a trial stop list for four weeks and note whether anyone, you included, misses them. If nothing changes in your work, they were comfort, not progress. If something suffers, move the habit back to continue with a clearer purpose.
The common thread
Each of the five myths replaces evidence with assumption. The start-stop-continue format is effective because it asks only for evidence from your own recent work. You do not need to invent a five-year plan. You need to write down what you did, what it cost and what it gave, and then pick a few small changes. A career moves in the direction of repeated small choices, and the lists make those choices visible.
A quarter in miniature
This sketch is invented, and the engineer in it has no name. At the end of a quarter, the engineer wrote down what had happened. Three evenings a week had gone to a new certification track. One internal talk had been given. A handful of short posts had been published, and one of them had brought a message from a stranger asking for help with a deployment problem. A pager rotation had taken most of one week.
The lists came out like this. Start: turn the stranger’s question into a longer write-up and keep the habit of documenting solved problems. Stop: drop the third certification evening, since the track had stopped teaching anything new. Continue: the internal talk, because it had led to two colleagues asking for pairing sessions. The engineer set one check for each item: a published write-up by the end of the next quarter, two evenings freed up, and a second talk booked. Nothing exotic, yet it pointed the whole quarter in a clearer direction.
A small outside example of sorting
Clear sorting makes any large set of options easier to handle. BestPilotsNow, an aviation discovery website, is built around its own set of tabs: people to find, schools, courses, reading material, a discussion area and written posts. Your own plan can do the same on a single page: one block for skills, one for visibility and one for relationships, each with its start, stop and continue lines.
A quarterly template you can copy
- Choose the three areas you care about this quarter, such as skills, visibility and income.
- Write what you did in each area, in plain words, with no judgement.
- Mark what produced results and what did not.
- Write two or three items under each of start, stop and continue.
- Give each item a check: a number, a date or a finished artefact.
- Pin the sheet somewhere you pass every week.
Final word
Careers in DevOps reward people who learn quickly and communicate clearly. A quarterly retrospective trains both: it makes you look at evidence, and it makes you write conclusions in plain words. The five myths above are only examples. Run the exercise once and you will probably find a few of your own. Replace them with checked facts, keep the habits that work and let the rest go.








