
Ask engineers what slows them down and the reply is seldom a grand architectural flaw. It is the login that expires mid-task, the local setup that takes a morning, the review queue that sits for days, the one command everyone has to run in the right order. In recent years teams have quietly changed how they talk about this sort of thing, and it is worth describing, because it shapes careers as much as tooling. The shift is toward treating small, repeating friction as work worth doing, one irritation at a time, rather than as weather to be endured.
From "that’s just how it is" to "let’s fix that"
Not long ago, a new engineer joining a team would be handed a wiki page of known quirks. Run this before that. Ignore that warning. Ask whoever happens to be around if the build hangs. The quirks were passed down like oral history, and the unspoken lesson was that a good engineer learns to live with them. Many experienced people still remember the pride of knowing where all the bodies were buried.
What has changed is the framing. Developer experience has become a recognised concern, and in many organisations someone is now responsible for asking how it feels to work in the codebase day to day. The vocabulary varies, but the underlying belief is consistent: friction that appears every week is a cost, and costs can be reduced. A new colleague’s first week has become a kind of inspection, because fresh eyes spot quirks that veterans stopped seeing years ago.
The monthly fix as a cultural practice
One of the more approachable forms this takes is a simple rule: each month, the team picks one repeating annoyance and fixes it at the root. Not a rewrite, not a campaign, just one thing. The practice has a few appealing properties. It is small enough to survive a busy quarter. It is visible, because everyone knows what this month’s irritation is. And it gives people a legitimate outlet: the engineer who has complained about the same setup step for a year finally has a place to put the complaint.
Teams that try it often describe a mood change before they describe a productivity change. The irritation had been a faint, constant background noise, and when it goes, people notice the silence. It also changes how newcomers are treated. A junior engineer who raises a snag is not told to get used to it; they are invited to put it on the list.
What this means for careers
For individuals, the trend is a quiet gift. Fixing a recurring annoyance well demonstrates several valuable skills at once: noticing a problem others have stopped seeing, finding its cause rather than its symptom, making a minimal change and communicating it clearly. Those are the habits that distinguish engineers as they grow. The progression traced in our look at the route from entry-level to seasoned DevOps engineer is full of moments where the difference was not raw technical depth but the willingness to own an everyday problem until it was truly gone.
It also gives early-career engineers an accessible way to contribute. Not everyone can redesign a platform, but nearly everyone can pick a small repeated snag, understand it and fix it. A record of such fixes is concrete material for a performance conversation and for a portfolio. For planning your own growth, our skills-and-projects roadmap for a DevOps engineer is a helpful companion, and a monthly fix log fits neatly into the projects portion.
A picture of one team’s year
Consider a small, imagined platform team that adopted the rule at the start of the year. In the first month they fixed the local environment setup that took half a morning. In the second, a deployment step that asked for a value people always had to look up. In the third, a flaky nightly job that emailed the wrong group. None of these made a conference talk. By the autumn the team had worked through a dozen irritations, and the thing they noticed most was that new joiners reached their first change in days rather than weeks. Nobody had planned that outcome; it emerged from the accumulation.
The story is illustrative rather than a measured result, and it is wise to treat claims about large productivity gains with caution. The safe claim is that removing repeated friction tends to make people feel more capable at work, and that is a worthwhile aim by itself.
Where the practice can go wrong
Like most good habits, this one has failure modes. Teams sometimes let the list swell until it feels like a backlog nobody will clear, which turns an energising ritual into a guilt exercise. Others pick fixes that are really disguised large projects. A third group fixes the symptom and calls it done, so the irritation returns in a new costume. One remedy covers all three: keep the scope to one, insist that the fix removes the cause, and write down what changed.
A glance at how others catalog things
As teams try to keep their lists of irritations organised, it can be interesting to see how other sites arrange collections. BestToolsX is a site built as a product directory for software and technology in preview form, with entries it labels as sample data, and visitors can explore its sections to reach a listing by product type or by relation to other technologies. It is a layout curiosity here, because the list of annoyances that matters is the one your own team keeps.
Questions worth asking your own team
If you want to find out where your team stands, a few quiet questions go a long way. What is the one thing a new joiner always gets wrong in their first week? Which command does everyone copy from an old message? What do people complain about at the coffee machine that never makes it into a ticket? Replies tend to be undramatic, which suits the purpose. They are exactly the sort of repeating friction that a monthly fix can remove, and asking the questions signals that you are willing to act on the replies. Teams that ask regularly tend to find that the list grows shorter over the year, not longer.
Looking ahead
It seems likely that attention to everyday friction will keep growing, partly because the tools for measuring it have become more accessible and partly because engineers have more choice about where they work. Teams that take small annoyances seriously tend to be pleasant places to be, and that matters when hiring is competitive. For the individual reader, the invitation is modest: notice what irritates you repeatedly, choose one, fix it properly this month and tell someone. Then do it again. Careers, like codebases, tend to improve through accumulated small repairs.