
A junior engineer once told me she had spent a whole winter promising herself she would “get serious about career growth.” By spring she had a bookmarked folder of courses, a stack of unread articles and no change in her working life. What finally moved things was almost embarrassingly small: for one week she read a piece of someone else’s production code every morning before opening her own tasks. Her story is a good excuse to clear away six myths that stop DevOps professionals from trying small habits at all.
Myth 1: “A habit is only real if you commit for the long haul”
This is the myth that blocks most beginnings. Faced with the idea of changing a routine forever, the mind produces objections instantly. A one-week trial removes them. You are not signing a lease; you are borrowing a routine to see whether it fits. The engineer in our story said that “just until Sunday” was the only wording that made her willing to start.
The commitment that matters is the review at the end. Put it in the calendar when you begin, and the trial becomes a complete little project with a start, a middle and a decision.
Myth 2: “You need an hour a day for it to count”
The habit she tried took fifteen minutes. She opened a repository she did not own, a colleague’s service, an open-source tool or a shared pipeline definition, and read one file with a single question in mind: why is it built this way? She did not run it, refactor it or comment on it. The point was exposure.
Small slots survive busy weeks. A trial that demands an hour will be abandoned by Wednesday, and then the lesson learned is “I am bad at habits”, which is not true and not useful. Fifteen minutes is enough to spot a naming convention, an odd retry setting or a clever shell trick you would never have invented yourself.
Myth 3: “Reading code is only for people who write a lot of it”
Many people in operations roles consider themselves script users rather than programmers and assume code reading is out of scope. Yet nearly every failure investigation starts by reading something: a configuration, a template, a job definition. Those who read widely arrive at an incident with a feel for what normal looks like. In her second week she noticed this herself, when an unfamiliar error pointed to a template she had skimmed earlier in the trial and she knew roughly where to look.
For people planning a long-term route into senior roles, the article on the a junior-to-senior route through DevOps engineering arrives at the same underlying point: breadth of exposure builds judgement more reliably than any single credential.
Myth 4: “If you skip a day, the experiment is ruined”
On day four she was pulled into an incident and read nothing. She felt the familiar urge to give up. Instead she wrote “skipped, incident” in her notes and resumed the next morning. When she reviewed the week, that gap mattered less than the pattern of the other six days.
Trials are not streaks. A streak punishes imperfection; a trial gathers information. A missed day tells you something about your schedule, and you can respond by changing the slot, not by reaching for guilt.
Myth 5: “You must write something impressive to show for it”
There is a temptation to turn every habit into content: a blog post, a thread, a presentation. For this experiment she resisted. Her only record was a line in a notebook each day, naming the file and noting one thing she would copy or avoid. Output can come later, after you know whether the habit is worth keeping. Trying to publish from day one adds pressure that makes people quit before the benefit appears.
That said, a short list of observations at the end of the week often turns out to be useful to teammates. Some people share theirs in a team channel and discover that others have been curious about the same service all along.
Myth 6: “Certifications and courses are the only real signals of progress”
Credentials have their place, and a clear overview such as the one in a rundown of certifications that can support a DevOps career can help you decide which are worth the effort. But progress in practical skill shows up in smaller ways: a quicker diagnosis, a more thoughtful review comment, a question that earns a nod from a senior colleague. Habits like reading other people’s work feed those moments without requiring an exam fee.
In her case, the signal came in week three, when a reviewer asked why she had chosen a particular retry approach and she could say, “I saw the platform team use it in their deployment job and the reasoning made sense.” That is a modest sentence, and a surprisingly powerful one.
How to run the same experiment yourself
- Choose a start day in a normal week, and tell one person what you are doing.
- Pick a daily reading slot of about fifteen minutes, at the same time each day.
- Read one file per day from a codebase you do not own, asking only why it is shaped as it is.
- Write one line in a notebook: the file name and a thing you would copy or avoid.
- Review on day eight: keep it, tweak the slot or the source, or drop it.
What the review taught her
When she sat down with her notes, six of seven days had entries. Two stood out as ideas she wanted to borrow immediately. One was an unremarkable file that taught her nothing, and she was glad to see that the habit did not need every day to be exciting. She chose to tweak: she kept the reading, but moved it to lunchtime because mornings were too often interrupted.
A closing thought, and an aside
Small trials also fit non-technical routines, such as sorting household paperwork or testing a new budgeting rhythm. If you are curious how a pre-launch finance tool introduces itself, the MoneyVoid site puts a product overview, an explanation page, a Q&A page and a blog in its menu. We mention it only to show how clearly labelled sections can make a new idea easier to approach.
The six myths share one theme: they make change sound bigger than it is. Shrink it to a week and a quarter of an hour, and you will find it far easier to begin, and far easier to stop if it does not suit you.