A learner once told me that her best DevOps habit began as a joke on a sticky note: “After the kettle clicks, I read one log line.” She laughed about it for a week, then noticed she had not missed a day in a month. The sentence did the remembering. That is the idea behind this list of eight “after I…” sentences, each one a small cue-and-action pair that DevOps learners and working engineers can borrow, adjust or discard.
The rules are the same throughout. The cue is something that already happens daily. The action takes under two minutes. The sentence is written down so nobody has to rely on memory.
1. After the kettle clicks, I read one real log line
Logs are the language of running systems, and fluency comes from exposure. A single line a day, picked from any service you can access, builds familiarity quietly. Read it, guess what produced it, and move on. If it puzzles you, note the question for later. The story at the top belongs here: the kettle is the cue, and the reward is a slowly growing sense of what normal looks like.
2. After I commit, I run the linter
Committing code is a near-perfect cue because it happens many times a day and has a clear ending. Attaching a linter or formatter run to it turns style checking from a chore into a reflex. If you use a pre-commit hook, the habit is built into the tool; if not, a single alias does the job. The point is the same: the commit tells your hands what to do next.
3. After stand-up, I glance at one dashboard panel
Notice the word “one.” A glance at a single latency or error panel takes seconds, and over weeks it teaches you the usual rhythm of the system. Teams that try to review every panel quit the habit. Teams that look at one panel keep it, and often start spotting oddities by instinct.
4. After I open the terminal, I type one command I do not know well
This is a learner’s habit. Open the terminal, then read the help text of a command you have used but never really understood, or try a new flag in a safe environment. Over a year, 250 small encounters add up to real depth. A learner in Osaka, as the story goes, picked up half her shell skills this way without ever scheduling a study session.
5. After I merge, I write a two-line note about what changed
Short change notes help future teammates, and they help you. The merge is a fixed event, and two lines is a limit small enough to respect. The note can say what changed and why, and nothing else. Over time, the notes form a readable history that saves hours of archaeology. The mindset connects to wider thinking about how modern delivery serves the people at the other end, as explored in a piece on how modern delivery shapes customer satisfaction.
6. After lunch, I read one paragraph about the field
A paragraph, not an article. Pick something from a newsletter, a vendor changelog or a community post. The cue is finishing the meal, and the habit keeps you loosely informed without the guilt of a growing reading list. For context on where the field is heading, a general piece such as a forward-looking read on DevOps in Japan and worldwide shows the sort of reading that fits this slot.
7. After I deploy, I watch the graphs for five minutes
This one comes straight from experience on call. Problems from a release often appear in the first minutes, and the person who made the change is best placed to read the signs. Make the deploy the cue, set a visible timer, and sit with the graphs until it rings. Many teams find that most of the value of this habit arrives in the rare release where something does look wrong.
8. After I close the laptop for the evening, I jot down tomorrow’s first step
Closing the laptop is a clean boundary. Writing a single sentence about where to start tomorrow lets you walk away without the unfinished task nagging at you. It also gives the morning a head start, since you know exactly where to begin. Keep it to one line.
How to pick from the list
Do not adopt all eight. The surest way to fail is to install them all on Monday. Choose one that matches a cue you really have, run it for two weeks, and only then consider a second. If the first sentence does not stick, the usual culprit is the cue, not your character. Replace it with something more dependable.
It helps to write the sentence in the exact form “after I …, I …”, because the wording forces you to name a concrete event. “When I have time” is not an event. “After I commit” is.
When a sentence stalls
Sooner or later one of the eight will stall. The usual signs are skipped days, a feeling of dread when the cue arrives, or a habit that quietly turned into a ritual of forty minutes. Treat each as a clue.
- Skipped days usually mean the cue is not as regular as you thought. Pick a firmer one, such as opening the terminal instead of “mid-morning.”
- Dread means the action has grown. Cut it back to the original two minutes and be strict about it.
- A ritual that swelled deserves a hard stop. Set a timer, and when it rings, shut the tab, however interesting the rabbit hole.
One more tip from people who coach new engineers: say the sentence out loud once a week during a one-to-one or a team chat. Hearing “after I commit, I run the linter” from a colleague makes it easier to borrow, and the shared wording becomes a small piece of team culture without any policy document.
Starting small, on purpose
Each item above is tiny by design. Two minutes feels like nothing, and that is the reason it survives bad weeks. When the pair has become automatic, you can lengthen the action or add a neighbouring one. Lengthening first is how habits die; people feel the weight of the new task before it has become automatic.
A thought for the shopping basket
The cue trick spills over into daily life. Some people use a basket checkout as the cue to glance at iReviewed, a website whose description says it holds brand pages and customer reviews about things Indian households buy and use, before paying. As with the engineering habits, it is the fixed moment that carries the weight, not the particular site.
A closing story
The learner with the sticky note eventually moved on to a new team. On her first day she wrote a new sentence: “After I sit down, I read the team’s most recent incident note.” She did not ask for permission or announce a plan. She simply attached a small action to the first thing she did every morning. Within a month she knew the system’s history better than people who had been there for a year.
That is what the list is for. Pick a cue, write the sentence, and let the day remind you.









