Writing

Long-form notes on Go, infrastructure and the CNCF projects I work in, with the real code and the tradeoffs. Sometimes a career lesson too.

~/Writing

  1. How database indexes work internally: B-trees, hash and composite indexes, EXPLAIN, why LIKE and regex skip them, and a real Prometheus fix.

    techdatabases
  2. Store dates in UTC, and test in more than UTC. Unix time, DST, RFC 3339, Go's time package and a real trace search bug that broke only behind UTC.

    techtimezone
  3. How Prometheus finds the series matching your query in milliseconds: inverted indexes, posting lists, Seek-based set intersection, and why negative matchers and regex are the expensive part.

    techprometheus
  4. Wiring OpenTelemetry traces, metrics, and logs into Prometheus and Grafana across microservices. The one move that matters (trace IDs in every log line), and the cardinality, sampling, and clock-skew traps that waste your time.

    infraobservability
  5. How internal microservices actually prove who they are to each other: OAuth2 client-credentials with Keycloak and OIDC, JWT validation via JWKS, and the clock-skew, key-rotation, and audience traps nobody warns you about.

    infrasecurity
  6. Building a cloud cost-reporting pipeline over Oracle CUR data: from a managed warehouse, to DuckDB in a serverless function that hit a ~200MB memory wall, to a long-lived VM query service. A lesson about separating the tool from where you run it.

    infratech
  7. Building a content-addressed file system on libp2p where every blob is verified by its own hash, so a peer can never lie about what it sent.

    techgolangweb3
  8. A scanner tells you which CVEs you have. We built a service that predicts the ones you probably also have but haven't found: ExploitDB co-occurrence mapping, Gemini for analysis, shipped as a Kubernetes microservice.

    securitytech
  9. A tiny Go package that blocks disposable and fake signups with four cheap checks cheapest-first, an auto-syncing blocklist, and the honest false-positive traps nobody warns you about.

    techgolang
  10. Most CVEs in your container image aren't in your code. Hardening 12+ OSS images (including IronBank/DoD) taught me the real move: cut CVEs ~80% by removing packages you never used, not by patching.

    infrasecurity
  11. Going from scared of a big repo to mentoring people into open source in two years, told through the real merged PRs that built the path.

    opensourceideology
  12. Building a round-robin HTTP load balancer in ~200 lines of Go, and the five quiet bugs (one of which go vet screams about) that reveal what real load balancing actually is.

    techgolang
  13. My first merged PR into Kubernetes was 25 lines of tests. Why a small, test-only change is the smartest way into a five-million-line repo.

    opensourcegolang
  14. Writing a tiny rootless container runtime in Go to see what a container really is: namespaces, pivot_root, and why Docker needs the reexec trick.

    techgolang
  15. Rebuilding the tooling behind jenkins.io, read by 11M+ people, on Antora and Gatsby during GSoC, without breaking a single URL.

    techopensource
  16. How I got into Google Summer of Code with Jenkins by showing up early at the edges, and why you contribute to get good, not after.

    opensourceideology