Activity
406 followers
-
Paul Shamus reacted on thisPaul Shamus reacted on thisAt the risk of sounding like a broken record, I wrote a blog post thats an overview for adopting ephemeral resources into your terraform codebases. I got good feedback that my last post was only addressing the sharp edges from ephemerals - this post aims to highlight and detail each use case, including the sharp edges! I would love your feedback or any "reactions" on the post! https://lnkd.in/g8Z2UHGf
-
Paul Shamus reacted on thisPaul Shamus reacted on thisI’m excited to share that I’ve started a new role as a Senior DevOps Engineer at Capital Group! From my first days here, it’s clear I’ve joined an incredible company with a strong culture and talented people. I’m looking forward to contributing, learning, and helping build great things with the team. And I have to say — the office is fantastic. This change also came with a location update. Dozer and I are now living in Renton, Washington, with spectacular views of Lake Washington. It’s a pretty amazing place to call home. Of course, Dozer has already taken his new responsibilities very seriously. In addition to supervising the local squirrel population, he has now decided that all birds in the area also require close monitoring. Excited for this next chapter — both professionally and for the new adventures here in the Pacific Northwest.
-
Paul Shamus reacted on thisPaul Shamus reacted on thisWe need to stop interviewing Cloud, DevOps, and SRE engineers like we’re hiring backend developers. If the role is about architecture, reliability, observability, scaling, and risk Why are we asking them to reverse-traverse a binary tree? We should be evaluating: How they design resilient systems How they prevent and resolve failures How they automate boring, repetitive work How they communicate under pressure How they make trade-offs when nothing is perfect Your top SRE might not be the flashiest coder in the room. But they might be the one who prevents a $2M outage at 3am. Most real DevOps\SRE code isn’t some elegant CS-masterpiece. It’s the automation that keeps systems alive: Pipelines that build and deploy Scripts that self-heal and recover Jobs that move data and validate it Tools that save hours of manual effort It doesn’t need to be clever. (Well sometimes it might be) It needs to work at scale, in production, under chaos. Hire the people who can keep the business running. Not just the ones who can whiteboard a tree traversal. And in reality the code we write is what we learn from class 101.
-
Paul Shamus reacted on thisPaul Shamus reacted on thisThank you HashiCorp and Jake Lundberg for inviting me to the HashiCorp Cloud Summit in Toronto. I truly enjoyed the event. The DevSecOps paradigm, the fast versus safe dilemma, and the lessons learned from the early stages of cloud adoption, from 1.0 to 2.0, 3.0, 4.0, and beyond were, in my view, absolutely on point. HashiCorp’s solutions sit at the core of addressing challenges we often don’t even realize exist, and events like this serve as moments of self-awareness that help us see and start tackling them. I also loved the fireside chat, not just because I was part of it, but because it felt like an honest conversation about technology, work, life, and everything in between. Thanks again to HashiCorp, Jake Lundberg and Raff Schirripa for the invitation and the great discussions.
Recommendations received
1 person has recommended Paul
Join now to viewOther similar profiles
Explore more posts
-
VIAcode
The new rule of infrastructure: scale the cloud, not the headcount We’ve hit a strange point in tech history. 🔸 A single engineer can now manage thousands of servers, and no, they are not secretly superhuman. Cloud-native configuration, automation, and Linux-based images changed the math. 🎆 In Azure, tools like Automanage, Desired State Configuration, and Policy mean this: 10,000 VMs ≠ 10,000 problems Consistency gets automated Human scaling is no longer the bottleneck The companies winning today are not the ones hiring armies of sysadmins. They are the ones designing environments that practically run themselves. If infrastructure still feels heavy, it is not you. It is your architecture. ✨ Ready to make your Azure environment manageable at scale? Explore Azure Assist for full managed operations: https://lnkd.in/eapAdusm #Azure #CloudManagement #DevOps #Automation #CloudArchitecture #VIAcode
-
Satishkumar Dhule
POV: It’s 2026 and your manual infrastructure is a ticking time bomb. 💣 If you’re still running terraform apply from your local terminal, we need to talk. Production-grade IaC isn't just about "making it work"—it’s about making it unbreakable. The 2026 Playbook for Terraform Elites: 🔒 State Isolation is King: Local state is a myth. Use S3/GCS with DynamoDB locking. Separate your Dev/Prod states or prepare for a $100k "oopsie." 📦 Modular or Bust: Stop copy-pasting code. Build versioned modules. Pin everything. If a provider update can break your stack, your stack is already broken. 🛡️ Zero-Trust Secrets: Hardcoding passwords in .tfvars? Straight to jail. 🚩 Fetch them dynamically from HashiCorp Vault or AWS Secrets Manager. 🤖 Policy-as-Code (PaC): Don't just plan. Use Open Policy Agent (OPA) to auto-kill any PR that tries to open Port 22 to the world. Stop clicking buttons. Start scaling logic. 🚀 What’s your #1 Terraform "lesson learned" the hard way? Drop it below. 👇 #DevOps #Terraform #CloudNative #SRE #InfrastructureAsCode
-
Myrle Krantz
What if you could easily understand how changes to your DB queries were influencing your end user experience no matter how complex the backend service landscape in between is? At Grafana Labs, we’ve always been about making complex things simpler. The first tool we built was Grafana, our single pane of glass. From there we grew a forest of open source tools: Mimir, Loki, Tempo, Pyroscope, Faro and more — while also contributing to projects like Prometheus and OpenTelemetry. Using these open source tools we built open observability cloud solutions for gaining deep insights into your cloud providers, your infra components, your k8s clusters, your applications, and your frontends. Now we’re adding a solution for Database Observability (in public preview) to help you understand query performance, and even get AI-powered suggestions for improvement! And we’ve integrated the insights from all these solutions with the Grafana Knowledge Graph so you can understand how the components of your systems behave and interact! Simplifying observability doesn’t mean hiding complexity. It means giving you the tools to master it. The ObservabilityCON 2025 keynote is available on demand so you can catch the Knowledge Graph demo, and all the exciting announcements we shared: https://lnkd.in/g_bSPhCK
-
Causely
🥁 Now Introducing... Causely’s MCP Server for automated remediation in Kubernetes and beyond. 🚀 When something breaks in a distributed system, the symptoms rarely tell the full story. Pod evictions, latency spikes, noisy neighbors: They're all just downstream effects of a deeper cause. This is where the Causely MCP Server comes in. It brings our Causal Reasoning Engine directly into your IDE, so you can: 🧩 Understand why incidents happen 🛠️ Apply the right fix — at runtime, config, or code ⚡ Remediate automatically with full causal context It's not another “rules engine.” Causely analyzes your system in real time and delivers explainable remediations where you already work, in MCP-compatible editors like Cursor and Claude. 📽️ Watch the demo, see it in action at KubeCon North America (Booth #1661) next week, or read the blog to learn more 👉 https://lnkd.in/eb_xnKkc
Explore top content on LinkedIn
Find curated posts and insights for relevant topics all in one place.
View top content