The many meanings of "DevOps," legacy software, & adulthood - Coté Memo #22
I’m in New York today for a quick meeting, ostensibly on DevOps, but as ever on how organizations can do software better. “DevOps” has increasingly become the term people use when they mean “doing all that new stuff, in new ways.” Vendors, like Pivotal, have tried to use the phrase “cloud native” to describe it, but that hasn’t stuck too much outside of the vendoring and chattering class. The key phrases, I’d say, are:
- “Cloud” as in “we’re putting together a "cloud strategy” and want the benefits of cloud technologies (automation, self-service, cost, bursting), private or public.
- “Agile” as the loose identifier for “what developers do” which isn’t used as much as it should be: I’m overly fond of pointing out that most people don’t really do enough of “agile.”
- “DevOps” as a catch phrase what the IT department does a whole to support all this and how its processes changes.
Occasionally, I’ll hear that someone is doing a “continuous delivery project” as the overall initiative that’s driving change.
All of that is why I’ve snarkily been calling my talks “Not actually a DevOps talk” because, really, DevOps has been up-leveled to anhttps://www.flickr.com/photos/cote/30513730244/in/datetaken-public/ all purpose wrapper for “the new shit.”
Legacy Software Sucks
Coté Content
Links!
Work/Life Balance
I like his recent album.