How to Set Up a Not-Now List for Your DevOps Studies in Six Steps

Rajesh Kumar

Rajesh Kumar is a leading expert in DevOps, SRE, DevSecOps, and MLOps, providing comprehensive services through his platform, www.rajeshkumar.xyz. With a proven track record in consulting, training, freelancing, and enterprise support, he empowers organizations to adopt modern operational practices and achieve scalable, secure, and efficient IT infrastructures. Rajesh is renowned for his ability to deliver tailored solutions and hands-on expertise across these critical domains.

A junior operations engineer once told me about the week she tried to learn everything at once. She had a container tutorial open, a monitoring guide bookmarked, a cloud course half finished and a colleague’s suggestion about a scripting language scribbled on her notebook. By Friday she could not explain any of them well. What changed her habits was a small, humble tool: a not-now parking list. This how-to walks through setting one up in six steps, so the next good idea you meet during your DevOps studies has somewhere safe to wait.

Step 1: Choose one home for the list

Decide where the list lives and stay loyal to it. A text file on your desktop, a note in your phone, or a page in a paper notebook all work. The only requirement is that you can reach it within a few seconds, because a slow capture tool invites you to follow the tangent instead. Resist the urge to build a clever system with tags and colours on day one. Plain is durable.

Step 2: Write the review date at the top

This step surprises people, yet it is the heart of the method. Before you write a single entry, put a date at the top of the page: the day you will read the list. Pick something regular, such as the end of each week. A list with a date is a plan. A list without one is a pile.

Step 3: Learn the one-line entry

When a tangent appears, write a single line with three ingredients: the topic, the source and a few words on why it caught your attention. For example: “blue-green releases, saw it in a talk, wonder how rollback works”. Then close the note and return to what you were doing. The skill is stopping after one line. If you notice yourself opening three tabs to learn more, you have started following the tangent, so close them and add them to the line as a pointer instead.

Step 4: Keep going with the day’s plan

Capture is only half of the move; the other half is returning. After writing the line, look at your original task and read the last sentence you wrote or the last command you ran. Re-entering the work at a clear spot makes it easier to resume. Over time, you will notice that tangents lose some of their pull once you know they are safe.

Many learners in Japan and elsewhere are balancing study with full-time work, so every minute of focused time counts. The discussion of where the field is heading in a forward-looking essay about the road ahead for the discipline is a reminder of how many directions are available, which is exactly why a parking list helps.

Step 5: Hold the review

On the day you wrote at the top, sit down with the list and read it from start to finish without acting. Then take each line in turn and choose one of three fates: study it soon, put it on the calendar for later, or delete it. Be brave with deletion. Interest that has faded after a week is information, not failure. Keep the session short; fifteen minutes is plenty. Do not begin studying a parked topic in the middle of the review, or the session will stretch and you will start to dread it.

Step 6: Adjust and repeat

After two or three reviews, look at how the habit is going. Are entries getting longer? Shorten them. Is the list growing without bounds? Review more often or capture less. Do you keep forgetting to look? Hook the review onto a routine that already happens weekly. Small adjustments keep the method alive. Teams who work this way often discuss it as part of how they handle change; the thoughts in this practical guide to DevOps and culture change management frame why small shared habits matter.

A story of the first month

Returning to our junior engineer: in her first week with the list she wrote nine entries and acted on none. At the first review she deleted four, scheduled three and moved two into a “maybe” section. The second week she noticed she had finished her container chapter, something she had failed to do for a month. She did not feel she was missing out. She felt, in her own words, that her curiosity had been given an appointment book.

Her list also gave her useful vocabulary. Terms she did not understand went on the list as questions, and later she looked them up in a reference such as a beginner glossary of essential DevOps terms at the review instead of in the middle of a lesson. That small change meant each lesson stayed intact.

Borrowing a lesson from release engineering

Professional teams do something very similar when shipping software. While preparing a release, an engineer may spot a cleanup or an idea and note it in a backlog to be looked at after the release. On the website Reloqui, which is built around release intelligence for engineering organizations, the focus is on understanding what a release contains. Whether you study that or not, the principle carries over to learning: keep the current piece small and clear.

Three small traps and how to step around them

The first trap is parking something that is actually your assignment. If your instructor has set an exercise for tomorrow, that exercise is not a tangent, however dull it feels. The second trap is writing entries so vague that they mean nothing a month later. “Look at networking” tells you nothing, while “overlay networks, mentioned in a lab, unclear how packets travel” gives future you a thread to pull. The third trap is treating the list as a guilt machine. A long list is not a failure; it simply shows a curious mind. Trim it at review and move on without ceremony.

A last tip for evenings after a long workday: if your energy is low, shorten the review to the five oldest entries. A short review done is better than a long one skipped.

Quick reference: the six steps

  1. Pick one easy-to-reach home for the list.
  2. Write the review date at the top.
  3. Capture each tangent in one line: topic, source, reason.
  4. Return to your task at a clear spot.
  5. Review on the date and choose study, schedule or delete.
  6. Adjust the habit and repeat.

You do not need to finish a course in order to begin. Open a blank note, write today’s date and next week’s review date, and wait for your next interesting detour. When it comes, you will know exactly where it goes.

Leave a Reply