18,750 req/s: precise, repeated, and three times wrong
Two phases of the same run measured the same service three times apart. What caught the wrong one was not a better statistic but a second method.
Blog
My hands-on development journal: PHP and Laravel, Go, JavaScript and TypeScript, developer tools and career. Architecture writing lives in Engineering. (Page 2/17)
Two phases of the same run measured the same service three times apart. What caught the wrong one was not a better statistic but a second method.
Building a strategy game alone meant cutting scope. The list of constraints ended up choosing every mechanic in the game by itself.
The only person with production database access went on holiday and diagnosis stopped. The need came down to four sentences; each became a design decision.
There is no right company type — only wrong matches. Closing the series: what each type teaches, and eight questions to ask in your next interview.
How to get a solid grasp of a codebase you have never seen: run it first, read the tests, trace one flow end to end, and understand before you refactor.
Growth is a staircase, and the same thing breaks on every step: the capacity of informal coordination. Reading the transition from three desks at once.
The first question asked when production goes down sets a company's culture for years. The human side: fear, silence, and what changes later.
Four index strategies on a 10M-row Postgres queue table: the winner didn't win for the reason I gave, and one setting turned it into a 1,635x loss.
The status meeting isn't an information tool, it's an insurance policy. A critique that takes meetings seriously before taking them apart.
In a corporate a raise hangs on a spreadsheet; in an owner-run company on a memory. A system doesn't change the outcome, only the language.
Work an agent finishes in days takes a week in a system running for years: there the cost isn't producing code, it's finding and proving the rules.
Knowledge stuck in one person's head and knowledge buried in a wiki nobody reads end up the same way: the reasoning behind a decision is unreachable.