My Tech Pivot

About

From Locks to Logs: My Journey into DevOps

For years, my world revolved around physical security, access control systems, surveillance networks, risk assessments, and the constant responsibility of protecting people and assets in the real world. I understood threats in terms of doors, badges, cameras, and human behavior. If something went wrong, it was tangible, you could see it, trace it, fix it.

Somewhere along the way, I started noticing a shift in my thoughts. Security wasn’t just physical anymore. My thoughts were expanding into networks, systems, and the invisible infrastructure powering everything around us. The same principles I relied on every day like risk management, layered defenses, incident response were all there, just translated into a different language. That realization sparked something, I should pivot into tech.

This blog is a record of my transition from physical security specialist to DevOps engineer. It’s not a polished success story (at least, not yet). It’s a work in progress full of learning curves, confusion, small wins, and the occasional frustration that comes with stepping into a completely new field.

I’m starting from the outside looking in. Learning concepts like automation, Kubernetes, cloud infrastructure, and containerization, things that once felt abstract are slowly becoming practical tools. At the same time, I’m discovering that my background isn’t a limitation, it’s an advantage. Security thinking doesn’t disappear in DevOps; it evolves into something even more critical.

Along the way, I’ll share what I’m learning, what’s challenging me, and how I’m connecting my past experience to this new path. If you’re coming from a non-traditional background, considering a shift into tech, or just curious about DevOps, you might find something useful here.

This is day one.