What the article calls "devops" I call just "ops." If the engineers writing the system also run the system, then they are "devops." "Ops" proper is much older

What the article calls "devops" I call just "ops." If the engineers writing the system also run the system, then they are "devops." "Ops" proper is much older than "at least 20 years" because they trace a direct line back to sysadmins, which have been around since forever. Out system works OK. We have devs, and ops, and devops. Devs run their new service with help from devops until it's stable and a runbook exists. Then, it's handed off to ops to keep running, with support if it breaks from devs if it's still in active development, or dedicated maintenance devops if it's mature. Not perfect, but pretty good, and efficiently runs the business as well as letting us iterate.