Skip to main content
Software Engineering Daily

Engineering in the Age of Agents with Yechezkel Rabinovich

50 min episode · 2 min read
·

Episode

50 min

Read time

2 min

Topics

Software Development

AI-Generated Summary

Key Takeaways

  • eBPF Instrumentation: Groundcover uses eBPF sensors to capture logs, metrics, and traces directly from the kernel without modifying application code, providing 100% visibility including unknown dependencies like third-party API calls that developers didn't explicitly instrument.
  • AI Code Review Strategy: With AI generating code at superhuman speed, code review must focus on test quality first, then context-dependent factors like performance for high-throughput systems versus simple input-output validation for low-risk libraries with no side effects.
  • MCP API Design: Effective LLM integration requires restricting API parameters beyond human SDKs, making certain fields required to force proper investigation flow, limiting results to 20 items, and exposing simpler endpoints first to prevent agents from requesting overwhelming data volumes.
  • Bring Your Own Cloud: Groundcover runs entirely within customer cloud accounts, keeping all observability data and AI analysis inside their security perimeter, addressing privacy concerns when LLMs process logs and traces that may contain PII or sensitive architectural information.

What It Covers

Yechezkel Rabinovich, CTO of Groundcover, explains how eBPF-based observability captures system behavior without code instrumentation, addresses AI-generated code challenges, and approaches root cause analysis in distributed microservices architectures.

Key Questions Answered

  • eBPF Instrumentation: Groundcover uses eBPF sensors to capture logs, metrics, and traces directly from the kernel without modifying application code, providing 100% visibility including unknown dependencies like third-party API calls that developers didn't explicitly instrument.
  • AI Code Review Strategy: With AI generating code at superhuman speed, code review must focus on test quality first, then context-dependent factors like performance for high-throughput systems versus simple input-output validation for low-risk libraries with no side effects.
  • MCP API Design: Effective LLM integration requires restricting API parameters beyond human SDKs, making certain fields required to force proper investigation flow, limiting results to 20 items, and exposing simpler endpoints first to prevent agents from requesting overwhelming data volumes.
  • Bring Your Own Cloud: Groundcover runs entirely within customer cloud accounts, keeping all observability data and AI analysis inside their security perimeter, addressing privacy concerns when LLMs process logs and traces that may contain PII or sensitive architectural information.

Notable Moment

Rabinovich describes creating a TypeScript library without knowing TypeScript by manually crafting test scenarios and letting AI generate implementation, never reading the actual code because the library's simple input-output nature made implementation details irrelevant for that specific context.

Know someone who'd find this useful?

You just read a 3-minute summary of a 47-minute episode.

Get Software Engineering Daily summarized like this every Monday — plus up to 2 more podcasts, free.

Pick Your Podcasts — Free

Keep Reading

More from Software Engineering Daily

We summarize every new episode. Want them in your inbox?

Similar Episodes

Related episodes from other podcasts

Explore Related Topics

This podcast is featured in Best Cybersecurity Podcasts (2026) — ranked and reviewed with AI summaries.

Read this week's Software Engineering Podcast Insights — cross-podcast analysis updated weekly.

You're clearly into Software Engineering Daily.

Every Monday, we deliver AI summaries of the latest episodes from Software Engineering Daily and 192+ other podcasts. Free for up to 3 shows.

Start My Monday Digest

No credit card · Unsubscribe anytime