Skip to main content

Posts

Cloud Cost Incidents Are Real: Why Budget Limits and Resource Policies Matter More Than You Think

  Cloud-native teams have long embraced chaos engineering, game days, and incident response to build resilient, scalable systems. We prepare for failure. We plan for it. We test it. But when it comes to cloud cost overruns? We often react —after the damage is done. It’s time to treat cost anomalies like operational incidents , because that’s exactly what they are: unplanned events that threaten system health—just in a different column of your dashboard. The Myth of Infinite Cloud = The Risk of Infinite Cost The promise of the cloud is elasticity. But elasticity without control is a budgetary time bomb. We wouldn’t let developers deploy to production without testing. So why are teams still allowed to: Launch GPU instances without a use case? Leave unused dev environments running for weeks? Exceed monthly budget targets without warning? It’s not about blame. It’s about systems thinking . Just like latency, throughput, and availability, cost is an operational signal...
Recent posts

How AI is Transforming DevSecOps: A New Era of Secure, Agile Software Delivery

 As software delivery accelerates and attack surfaces grow, traditional DevSecOps practices are being pushed to their limits. The integration of artificial intelligence (AI) into DevSecOps workflows is not just a trend—it’s a strategic imperative. AI is driving a seismic shift in how we manage code quality, automate security, respond to threats, and enable secure innovation at scale. In this post, we’ll explore the key ways AI is improving DevSecOps and why forward-thinking organizations are embedding it deeply into their pipelines. 1. Proactive Threat Detection and Response In modern CI/CD pipelines, code moves fast—sometimes too fast for human eyes to catch every vulnerability or misconfiguration. AI helps shift security left and right by: Analyzing code and dependencies with natural language processing and ML to detect hidden vulnerabilities, insecure APIs, or anomalous changes during commits. Real-time anomaly detection in production environments using AI-powered o...

Cloud Ops: The New IT for the Cloud Era

Over the past few months of interviewing and researching dozens of companies—particularly small to mid-sized SaaS businesses—one pattern keeps emerging: the desire to stand up a Cloud Operations (Cloud Ops) organization. It makes sense on the surface. Cloud is now the infrastructure of choice, so naturally, someone needs to “own” it. But what’s unfolding in practice often misses the mark. Many companies are attempting to solve growing cloud complexity by taking all their DevOps, SRE, and platform engineering talent and consolidating them into a Cloud Ops team. The idea? Share them across product teams so no one gets overwhelmed. If that sounds familiar, it should. It’s the same centralization tactic used by traditional IT for decades. And it's creating the same problems. When Cloud Ops Becomes Old IT in Disguise Here’s the playbook we’re seeing: Move DevOps, SRE, and Ops into a central Cloud Ops team. Let them handle infrastructure, CI/CD, monitoring, and cloud securit...

Why leaders need to learn the word No!

  Other, alternatives like "Not right now" or "Can we stop working on x and focus on this?” While it's important to meet customer requests, allowing them to get everything they want can negatively impact our employees and take time away from items help all customers. Agile has streamlined the process of request and delivery, but it can also lead to wasting time on less important tasks. To protect our employees and our business, we should focus on the highest priority items that will improve our MESS. M-Maintain Efficient Operations E-Expand Customers or Revenue S-Save Expense S-Security Improvements

Learn Anti-Leadership from Basecamp

 There are many different articles out there and Twitter comments about the Basecamp drama.  I am not going to post any here because it might seem biased depending on the article.  Google them yourself.  In short, Basecamp made a policy to not allow political discussions at work.  Coinbase did this previously too and applauded Basecamp for it.   Apparently, for years there has been a list of funny customer names at floating around Basecamp.  This list or even the knowledge that Basecamp had a list, was disturbing to some employees.  Also, some employees tried to start a Diversity and Inclusion practice.  Despite how much the founders of Basecamp promoted DI, they didn't feel they were being taken serious.  They felt the company was only about the founders and not about employees.    If this isn't enough, the founders debated and even called out employees for their comments regarding the topics, publicly.  This is my s...

Character and Integrity above all

 How do you lead without stress?  I am finding that many leaders are under a lot of pressure, not healthy and not sleeping well.  A good leader may have ups and downs but their trust should never be questioned.  Your day to day work will be hard and require a lot but when you know you are making decisions with high integrity and treating your employees right, you should sleep well each night.   Each day is a new day.  You should begin each day with some quiet time, exercise and make a plan.  Then, you do your best that day.  Solve problems, help your team, mentor leaders, architect or remove toil.   Above all, do everything with character and integrity because when things get hectic or when you have to move on, you know you led with trust and integrity.   People will remember the way you lead more than what you did.  If you are weak in an area, hire someone to fill that need or go learn more.  This is part of leadersh...

Set a Vision and reach goals

 Leaders should be setting the vision for the company or team.  When tech teams are always jumping from priority to priority, they will get frustrated.  When you set the vision, show the team you stand behind it.  Get the buy in from your team.  The companies ability to set a vision for a team or project and work towards it, will set long term culture and retention.  Thoughts: 1. Create a long term vision with short term goals. 2. Use OKRs to communicate the actions and measurements of the goals. 3. Post regular messages or videos about the goal progress. 4.  You may never reach the full vision but you worked toward it. 5.  If you don't the vision or goals, ask around.    Lead with a daily passion for the companies vision.