HN user

th3tekllc

2 karma

For 20 years, I've been at the bleeding edge not following trends, but building infrastructure that becomes industry standard 2-5 years later. MongoDB at production scale before it was mainstream (Cisco acquired the company). Platform engineering before it had a name. Golden paths before Spotify popularized the term. I don't just implement I create categories.

Most recently at large cloud provider, I led the largest HCLS cloud platform engagement in history. The infrastructure we built enabled their generative AI strategy their CIO keynoted about it at a major cloud conference. The engagement became the reference architecture for the entire vertical and generated $20M+ in downstream pipeline.

Now I'm pioneering OutcomeOps: the next evolution beyond DevOps. DevOps gave us speed and stability, but it measures activity (deployments, MTTR) not outcomes (business value delivered). OutcomeOps ties engineering directly to business results. Context Engineering is how you implement it in the AI era—grounding AI code generation in organizational knowledge so engineers focus on outcomes while AI handles syntax.

Posts2
Comments6
View on HN

I spent 2.5 years running the largest HCLS engagement at one of the big three cloud providers. 55 engineers, $18M revenue, $31M in bookings. My peers wrote glowing feedback. My customer's CIO keynoted the company's flagship conference. My review said I needed improvement.

This is about why that happens — and why it's not just my story.

[dead] 8 months ago

The Uncomfortable Truth About Offshore

Every enterprise has the same story.

You hired TCS, Infosys, Wipro, or Cognizant. The pitch was compelling: $45/hour versus $150/hour. The math was obvious. You'd save millions.

Then reality hit.

You don't have 200 engineers in India. You have 12-18 real shippers in the US and a 180-person tax.

I've seen this pattern repeat across cable, big pharma, insurance, and more. At one Fortune 500, they had 55 engineers on the books. Only 3 were trusted to deliver end-to-end without handholding. The other 52? They generated work for those 3.

Enter AI (But Not How You Think)

Here's where it gets interesting.

Everyone's talking about AI coding assistants. Cursor raised at a $29 billion valuation. GitHub Copilot is on every developer's machine. The narrative is "AI will make developers faster."

That's thinking too small.

The real disruption isn't making your 200 offshore engineers 20% faster at typing. It's eliminating the need for 180 of them entirely.

[dead] 8 months ago

Gene Kim was right in "Vibe Coding" the implementation bottleneck is gone. What he didn't say out loud? The organizational bottleneck is next.

Just published: "The Death of the Traditional Product Owner" In it, I argue that 90% of Fortune 500 Product Owner roles as practiced today will cease to exist within 24 months.

Not because AI is cruel. Because they were always a workaround for a broken system.

The best POs? They're about to become the most valuable engineers on the planet. The rest? They're about to discover what Ops teams learned in 2015.

After 20 years of transforming engineering organizations (Pearson, Aetna, AWS ProServe, Comcast), I've seen this pattern before: 2014: "Containers will never replace Ops" 2016: "Serverless is just a fad" 2025: "Product Owners are essential"

We know how those movies ended.

OutcomeOps makes it safe, auditable, and compliant for engineers to own outcomes directly - even in regulated environments.

No more telephone games. No more 12-18 handoffs per feature. No more requirement translators.

Just engineers shipping business value.

P.S. If you're a Product Owner feeling uncomfortable right now - good. That feeling is your starting line.