Muhammad A.

I got introduced to DevOps during a simple conversation with my dad. It went something like: “You're about to be an adult, eh?” “Yeah, but I’ve got a lot to figure out.” “Like?” “A career.” “Why not DevOps?” “Sure.” A few short videos and whitepapers later, I realized that my past 16 years were basically DevOps Culture - underpromising and overdelivering, prioritizing reliability, repeatability, automation, ownership, and accountability. I naturally gravitated toward cross-functional teamwork over siloed blame games. So I poured my existing coding knowledge, obsessive learning style, and way-too-much free time into mastering tools like Terraform, Jenkins, GitHub Actions, AWS (EC2, IAM, SGs), Prometheus, Grafana, Splunk, Datadog, OTEL, and GROK (among a few others). I made sure that a single command either deployed an app - or emailed me a hyperlinked error summary with pipeline context. That level of delivery power only comes from hands-on work - no amount of tutorials or docs could’ve taught me what trial and error did. Now, with nearly a year of higher education behind me and even more time in the DevOps world, I’m finishing my Associate’s in Computer Science at an accelerated rate while heading straight into a Bachelor’s (and eventually a Master’s in IT). My projects and real-life situations have taught me how vital DevOps culture is - from monitoring infra and behavior, to communicating findings, applying fixes, and following through. Sometimes the budget gets blown (on EC2s or IRL emergencies), and you learn to provision and negotiate. Sometimes tools break or don’t fit - and you learn it’s better to analyze your stack before you’re mid-crisis on a deadline. That taught me punctuality, planning, and how to perform under pressure - skills I now carry into every pipeline, ticket, or meeting I touch.