How Blameless Culture Transforms Engineering Teams
Briefly

How Blameless Culture Transforms Engineering Teams
"I was supposed to do four years, go through university and head back home for family business, decided I liked tech too much. I got my first job at EMC running their networks across I would say a few hundred offices, which was really interesting. From there, I made my way into an ops role, which is where a lot of what we do at RapDev began."
"Spent a good amount of time running a NOC, SOC, a few other ops roles. And back then, it was very heavy on the technology stacks versus the services as the world has transformed today. We're responsible for storage, we're responsible for security, responsible for mail services and et cetera. That over time has evolved into being responsible for different services regardless of the components that build them. That's basically how I ended up here."
Grew up in Bahrain and moved to Boston for college in 2006 before staying to pursue a technology career. Began at EMC managing networks across hundreds of offices, then transitioned into operations roles. Spent significant time running a NOC and SOC and handling responsibilities like storage, security, and mail services. Observed a shift from focusing on individual technology stacks to owning services irrespective of underlying components. Evolved into roles centered on service responsibility and operations, which shaped the approach to building and maintaining reliable systems.
Read at InfoQ
Unable to calculate read time
[
|
]