Archive

1046 posts · Page 48 of 88. ← Blog

Pratik Dhanave · ·11 min read

context: Cancellation, Deadlines, and Values

How Go's `context` package carries a cancellation signal, a deadline, and a small bag of request-scoped values across every API and goroutine boundary in a request — and the handful of rules that keep it from leaking or lying to you.

How Go's `context` package carries a cancellation signal, a deadline, and a small bag of request-scoped values across every API and goroutine boundary in a request — and the handful of rules that keep it...

Pratik Dhanave · ·6 min read

An Eval Regression Gate in CI

Treat agent output quality like a test. A baseline file plus a gate that fails the build on regression turns "the agents got worse" into a red X.

Agent systems rot because nobody catches quality regressions until users do. A committed baseline plus a gate that fails the build turns the agents got worse into a red X and a reviewable diff in the pull request.

Pratik Dhanave · ·9 min read

Unit Economics

A company can grow revenue explosively, raise huge rounds, and dominate headlines — and still be doomed, if it loses money on every customer. Unit economics is the question underneath all the aggregate financials: does a single customer, on its own, make money? Get that right and scale is the amplifier of a good thing; get it wrong and scale just multiplies the losses. It's the most important economic idea for judging whether a business actually works — and the one flashy growth numbers most often hide.

A company can grow revenue explosively, raise huge rounds, and dominate headlines — and still be doomed, if it loses money on every customer. Unit economics is the question underneath all the aggregate financials: does a single customer, on its own, make money? It's the most important test of whether a business actually works.

Pratik Dhanave · ·13 min read

Atomics and the Go Memory Model

What a data race actually is, why it is undefined behavior rather than "just a wrong number," the happens-before rules that make concurrent code correct, and when `sync/atomic` is the right tool — and when it quietly is not.

What a data race actually is, why it is undefined behavior rather than "just a wrong number," the happens-before rules that make concurrent code correct, and when `sync/atomic` is the right tool — and when...

Pratik Dhanave · ·6 min read

The Cheapest Reliable Executor Wins

Deterministic rules get first refusal at zero model cost. Only the unknown cases escalate to graduated AI agents. A human approves anything that mutates.

Deterministic rules get first refusal at zero cost and still fire when the model is down; only the novel long tail escalates to graduated agents; a human approves anything that mutates. Build a ladder, not a model call.