dannyman.toldme.com

Code is Infrastructure

They say “infrastructure is code” – the DevOps Mantra. I say it myself.

I don’t call myself DevOps. (My employer does and I don’t argue with a paycheck.)

I write code to manage infrastructure. I am a DevOps Practitioner.

But …
I am large.
I contain multitudes.
I call myself a Systems Administrator.

Because, really:
Infrastructure is computers
Computers are largely code
Computers are more than code
There are cables and latches and screwdrivers involved

Infrastructure is also power, network, site planning, service agreements, security standards and processes and audits, recruiting, staff training, on-call schedules and standards, vacations, physical and mental health, procurement, shipping, payments, budgets. Infrastructure is so much more than code.

(On my current team we also advertise: Engineering Support services, Information Technology services, Audio-Visual services, Bicycle Maintenance, and Wildlife Removal. Multitudes!)

Infrastructure is not code; Code is infrastructure

And yeah you need to manage infrastructure resources effectively. Managing the code infrastructure means source control, automated tests, validation, pull requests, managing build/deployment infrastructure, &c.

There are cloud-only DevOps who wash their hands completely of the physical realm. All hardware is just an API. Good for them. They seem to spend a lot of time in meetings.

This is what you might see one day if you are a server who has been having an especially rough time.

For me … I’m a “full stack” engineer. Maybe I’m a full rack engineer. I have, in my career, managed most of the infrastructure components listed above. I’m grateful to work on a growing team that allows me to focus somewhat.

I keep a broad lens.
I enjoy managing infrastructure with code.
That frees up time and attention for the rest of the adventure.

Based on https://sfba.social/@dannyman/117061052052787533