Can Other Fields Teach You DevOps? Your Questions Answered

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.

Newcomers to DevOps tend to circle one question: where do the good ideas come from, and why do so many of them sound like they were invented in a factory, a hospital ward or a cockpit? The short answer is that many were. This question-and-answer guide goes through the points learners raise most often about borrowing methods from other fields. It is meant to be read casually, in any order, so jump to whichever question looks closest to your own.

Why learn DevOps ideas from fields unrelated to software?

Because the underlying problems are not unique to software. Teams everywhere have to hand work between people, catch mistakes before they reach customers, recover calmly when something fails and improve gradually without stopping the business. Fields with physical consequences, such as manufacturing, aviation and emergency services, were forced to solve these problems early and carefully. When you borrow from them, you skip some of the slow trial and error.

It also helps with a very human difficulty. Learning a technical area from within often means absorbing its jargon before its logic. Looking at the same idea in a field you already understand, like cooking or sport, lets you see the logic first.

Which neighbouring fields are most worth looking at?

There is no official list, but a few come up again and again for good reasons.

  • Manufacturing: small batches, visible queues and stopping the line when something looks wrong. Much of the vocabulary around flow in software delivery has roots here.
  • Aviation: checklists, structured briefings and open reviews of what went wrong. The culture treats reporting an error as a contribution rather than a confession.
  • Theatre and live events: coordinating many specialists on a fixed timeline, with one person calling each step.
  • Libraries and publishing: cataloguing, version control of manuscripts and editorial review before anything goes out.
  • Agriculture: controlled trials, seasons and patient measurement.

Pick the field whose daily problems feel closest to yours, not the one that sounds most impressive.

Is it not risky to copy ideas from industries that work so differently?

It is, if you copy blindly. A better word than copying is translating. A cockpit checklist works because the steps are short, ordered and checked aloud. A direct copy into software would be a hundred-line document nobody reads. The translation is a handful of critical items before a release, tailored to your system.

Before adopting anything, put two questions to yourself. What problem was this method originally built to solve? And do I have the same problem? If the answers line up, adapt it. If not, leave it behind and no harm is done.

How do I find a method worth borrowing?

Start from a pain point, not from a catalogue of methods. Write down one thing that keeps going wrong in your work or study, for example late discoveries of mistakes. Then ask a friend or colleague from another trade how they catch mistakes earlier. A baker might talk about tasting dough before it is baked. A builder might describe checking measurements before cutting. You are collecting raw material, and you will usually find at least one idea you can try within a week.

Does DevOps itself have a history of borrowing?

Yes, and that is part of why the question is worth asking. The way delivery practices have developed over the years shows repeated exchange with other disciplines, particularly around flow, quality and teamwork. If you want the longer story, this look at the path from siloed operations to cloud-native engineering shows how the field changed shape over time.

What about the people side? Surely tools matter more than culture?

Ask any experienced engineer and most will say the reverse. The borrowed ideas that last are mostly about how people work together: who decides, how information moves, how disagreements surface early. A good companion read on this is the discussion of managing cultural change as DevOps practices spread. Methods from other fields tend to stick for the same reason, because they were designed around human habits as much as technical steps.

How do small teams use borrowed methods without much process?

Keep it tiny. One idea, one change, one review date. A team of four does not need a formal programme. It can adopt, say, a short pre-release checklist borrowed from aviation, run it for a month and see whether surprises drop. Teams that bring together different skills under one roof often find borrowing easier, since each person can nominate a field they know. The piece on how mixed-skill teams are structured and what trips them up is relevant if you are building that kind of group.

Do I need work experience before I can borrow anything?

No. Students can run the same experiments on their own study habits. A learner preparing for an interview might borrow the pre-flight briefing from aviation: spend two minutes before each practice session stating the goal, the first step and the signs of a successful session. A hobbyist running a home server might borrow the stock-room habit of labelling shelves, which in practice means naming every service and noting where its data lives. Small, personal settings are ideal places to test ideas because mistakes there cost nothing.

How do I persuade teammates to try something borrowed?

Describe the problem first and the method second. Nobody gets excited about “a technique from shipbuilding,” but most people will listen to “we keep finding the same bug after release; here is how another trade catches it earlier.” Offer a time-limited trial, say three weeks, and agree what you will look at afterwards. People accept an experiment far more readily than a permanent rule, and a trial that fails costs everyone very little.

Can borrowing go wrong?

It can. The classic failure is adopting the visible parts of a method without its purpose. A team might copy a stand-up meeting from another discipline, hold it for an hour and wonder why nothing improves. Another is borrowing from a field whose constraints are very different, such as copying heavy sign-off procedures from a setting where one mistake is irreversible into a setting where releases can be rolled back in minutes. Each time, the cure is the same: go back to the original problem and ask what the method was really protecting.

How will I know a borrowed method is working?

Decide in advance what you expect to see. If the method is a checklist, you might expect fewer last-minute fixes. If it is a briefing habit, you might expect fewer misunderstandings between shifts. Write the expectation on paper and look at it after a month. Be frank about what you find, and retire whatever has not justified the time.

Beware of one common trap: judging a method by how professional it feels. Rituals can look impressive and change nothing. Judge by the outcome you named at the start.

Where can I read more broadly while I learn?

Variety helps. Gyan School describes itself as one landing page for engineering learning, and shows a menu covering a blog, a forum and an LMS alongside four short tracks that run from software engineering to DevOps and data-focused work. Treat it as one starting point among many, and add reading from outside technology so that ideas from other trades have a chance to reach you.

What is a good first experiment?

Choose one repeated task in your own routine, perhaps preparing a demo, deploying a small project or reviewing a classmate’s work. Ask which other field does something similar every day and how they keep it reliable. Pick one habit from that answer, try it three times and record what changed. That small loop of curiosity, trial and review is the real skill. The specific method is only the vehicle.

Leave a Reply