Jevons Paradox Is Not a Law of Nature
Efficiency sometimes increases consumption, but not always. Jevons' paradox is a conditionally useful idea, not an automatic rule.
Read post →Mostly on backend systems, platforms, and the parts of distributed systems that decide whether anything else works.
Efficiency sometimes increases consumption, but not always. Jevons' paradox is a conditionally useful idea, not an automatic rule.
Read post →Why `@Transactional` is one of the most dangerous comforts teams carry from monolith-era Java into distributed systems.
Read post →What it took to build a Backstage plugin that made the TCS Labs internal developer platform easier to discover, navigate, and operate.
Read post →Flaky tests are not random. They are bugs with a probability attached. A practical method for actually fixing them.
Read post →Managing up as an engineer means proactively building a collaborative relationship with your manager so both of you succeed. It is not about manipulation; rather, it requires anticipating your manager’s goals, communicating technical complexities simply, and removing surprises.
Read post →Logs, metrics, and traces solve different problems. A practical guide to which to reach for, and what to instrument first.
Read post →A field guide to the database indexing mistakes that only show up under production-shaped load.
Read post →Channels are not the default answer in Go. A look at when a mutex, a sync primitive, or a single goroutine is the better tool.
Read post →Why idempotency keys belong in the API contract from day one, and how to design them so retries are safe.
Read post →Notes on building an internal developer platform with CNCF Meshery as the operational core.
Read post →