Your systems call the same database payments-db, payments-postgres, and cloud-sql-payments. An engineer knows it's one database. No string comparison does.
Our CTO, @cgwu0530, covered three key problems that make building a context graph for an AI SRE harder than it looks.
👉 Read the article here: tinyurl.com/mrxjxxvy
🤖 Made with AI
1
83
A backend service slows down. Within a minute, a hundred alerts fire — the gateway, the API layer, every downstream metric reporting the same failure.
Somewhere in that pile is the one alert that actually matters. Finding it under the noise is what costs on-call teams the most time.
Momento Co-Founder and CTO @dymxzvf shared her fix with our CEO @vsreekanti Sreekanti, and it isn't "alert less" or "alert more." It's alerting at the right layer.
"If the backend errors, the gateway in front of it is going to error too, because one depends on the other. Page on both as independent failures, and you've turned one problem into two."
Knowing where to place an alert also requires knowing the dependency graph underneath it — which services fail into which, and which signal actually points to something new versus which one is just an echo.
That's a hard problem for a human to hold in their head across hundreds of services. It's an even harder one for an AI SRE agent trying to decide what's worth paging someone about at 2 a.m.
👉 Read the full piece here: tinyurl.com/yvjbkfb8
🤖 Made with AI
Are engineering teams actually better off with AI coding? Spoiler: nobody seems to know yet. And we made a video: "The Last Architect"
Code volume is up. Velocity is up. And token bills are definitely up.
But when @cgwu0530 talks with engineering leaders, many still cannot say whether productivity or ROI has improved, or even how they would measure it. He wrote about that recently in a post called "Winter Is Coming for AI Engineering."
But here's where it got interesting, at least when it comes to how crazy ideas take shape inside companies. At our Thursday All Hands, Kaveh Karimiyanha hosts Kaveh’s Corner, part tech-news comedy monologue, part “guess which company name is fake,” and occasionally an AI-generated song about something company or industry related.
Quick aside: Kaveh brings good energy. So Kaveh turned Chenggang’s blog post into a song. And that song was mighty catchy.
Caught up in the excitement of the moment, the marketing guy, Peter Farago, blurted out: “That’s so cool. I’ll turn it into a video!”
Several days and an unreasonable number of hours later, after rebuilding the song, rearranging lyrics, developing characters, constructing an entire visual world, and repeatedly asking AI to generate scenes that were not nonsense, here we are.
Peter looks haggard.
The result is The Last Architect, a story about token maxxing, growing review loads, code sprawl, lost context, and what happens when engineering organizations reward output volume without knowing whether the system is actually getting better.
Peter is pretty sure the video has a beginning, a middle, and an end. Either way, the song is definitely a banger.
The original post that started all of this:
Winter Is Coming for AI Engineering
tinyurl.com/2jwhus78
Every VP of Engineering is spending money on Claude Code or Cursor right now. Most can't say what they're getting for it.
Adoption came first. Measurement hasn't caught up. And that can't last.
Broad coding agent usage is changing the way we build and how fast we produce code. But it also comes with a variable token tax and questions about code quality.
Are we really better off, and more importantly, can we even measure it well enough to know?
Herald Co-founder & CTO, @cgwu0530, breaks down why this is happening, and why a reckoning might be closer than most budgets are ready for.
👉 Read the full post: tinyurl.com/4htjer8d
Herald is excited to partner with @ClickHouseDB to bring AI DevOps intelligence to every team on ClickStack, with up to $25,000 in free usage.
Now teams can reason over everything ClickStack aggregates — logs, metrics, traces, session replays, and errors — to catch incidents early, find root cause in minutes, and answer any question about their systems.
Store it all on ClickHouse. Understand it all with Herald.
👉 Read the blog post: tinyurl.com/5ck7a63w
👉 Check out the program: tinyurl.com/3t3n763h
Customer Case Study: @SnorkelAI hits 93% accuracy with Herald, no runbooks. Their demo of Herald won the team Snorkel's internal Engineering Excellence Award.
Snorkel AI connected four data sources to Herald and gave it nothing else. No runbooks. No historical root cause analyses. No Slack history.
Herald ingested all four in hours and returned its first correct root cause analysis within two days.
Their PM ran the agent through 90 real engineering tasks. It got 93% right.
In the first two weeks live in production, 27 engineers root caused 52 incidents.
Most #AIDevOps agents come with a setup tax. Weeks of writing runbooks, tagging incidents, and building a knowledge base before you see anything useful. Snorkel skipped all of it.
Kartik Mathur, Director of Engineering at Snorkel AI, co-authored the case study with Herald CEO @vsreekanti.
👉 Read the full case study: tinyurl.com/46u9c62n
Herald has been named to the The InfraRed 100, recognizing the top private companies defining the future of cloud infrastructure.
Thank you to the @Redpoint team for the recognition.
Want to try Herald? We now offer Herald CLI — completely free, full-featured, and up-and-running securely from your terminal in minutes.
Join the waitlist: lnkd.in/ge37zaaU
See the full list of 2026 InfraRed 100 honorees and accompanying industry report: redpoint.com/infrared/report…
1
80






