Content area
Full Text
There are numerous approaches to in-house development; Davey Winder explores one that focuses squarely on efficiency
- NoOps? What does that mean?
Well, you've heard of DevOps: development and operational teams working together to ensure you end up with software that does what's needed, and staff who know howto work it effectively. The NoOps approach is more radical: instead of blurring the boundaries, the aim is to create software that doesn't require an operational team at all by automating everything to the maximum extent possible.
- So it's a way of slashing headcount?
In theory, perhaps. Realistically, you're still going to need humans to operate your applications - even Forrester, the research company that originallycoined the term NoOps, admittedthat some "ops" would likelyremain. However, if your apps are designedaccordingto NoOps principles, staff can spend lesstime on mundanetasks and more focusing on things that are directly beneficialtothe business.
- What about security? Is DevSecOps no longer the holy grail?
To get finicky, I'd arguethat the holy grail was neverDevSecOps, but rather SecDevOps. In other words, security should be right at the...