<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:content="http://purl.org/rss/1.0/modules/content/">
  <channel>
    <title>Go on Shubham Singh</title>
    <link>https://1shubham7.blog/tags/go/</link>
    <description>Recent content in Go on Shubham Singh</description>
    <generator>Hugo -- gohugo.io</generator>
    <language>en-us</language><atom:link href="https://1shubham7.blog/tags/go/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Agent Evals: How to Know a Change Made Your Agent Worse</title>
      <link>https://1shubham7.blog/agent-evals/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      
      <guid>https://1shubham7.blog/agent-evals/</guid>
      <description>Normal code has tests; agents need evals. What an eval harness is, the vocabulary that goes with it, how I would build one in Go for an SRE agent working against Kubernetes, why pass^k matters more than pass@k for ops, the tools that exist (and the one OpenAI is shutting down), the ways a harness&amp;#39;s numbers lie to you, and the habits that keep a suite useful.</description>
    </item>
    
    <item>
      <title>Learning Rust as an SRE: The Parts That Matter for Infra Tooling</title>
      <link>https://1shubham7.blog/rust-for-sres/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      
      <guid>https://1shubham7.blog/rust-for-sres/</guid>
      <description>I learned enough Rust in a weekend to read, review and debug the CLIs, API clients and daemons that show up in infra work. This is the subset that mattered, the compiler errors you will actually hit, and the parts of the language I deliberately skipped.</description>
    </item>
    
    <item>
      <title>Site Reliability Engineer (Obmondo)</title>
      <link>https://1shubham7.blog/experience/obmondo/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      
      <guid>https://1shubham7.blog/experience/obmondo/</guid>
      <description>Outline Worked as an SRE, handling production systems and managing Kubernetes clusters and Linux servers across both internal and customer environments. As the youngest SRE at Obmondo, regularly took ownership of production alerts and incidents, performing root cause analysis and implementing long-term fixes. Led the rewrite of the most business-critical internal tool, improving its reliability, testing, and integration into GitOps workflows. Authored and improved a large part of the company’s ISMS, strengthening both the company’s and customers’ information security.</description>
    </item>
    
  </channel>
</rss>
