Just Ask
Ask me anything about software architecture, careers, PHP, Go and the craft of building software; I answer here, in the open, for everyone.
Whatever's on your mind, don't hold back. Questions reach me directly; I answer the good ones and publish them on this page. Your email is never published.
Yes — this is the textbook use for a partial index. WHERE status='pending' indexes only a few thousand rows; small, cache-friendly, skips the millions of dead ones. Include the ORDER BY column and pair it with SKIP LOCKED.
Pass r.Context() into every downstream call: QueryContext, NewRequestWithContext. If you use context.Background() anywhere in the chain, cancellation breaks. Use WithoutCancel for side effects that must survive.
Use a custom cast — that's exactly what casts are for. One CastsAttributes class works across every model; accessors mean per-model duplication. Integer cents in the DB, an immutable Money on the model.
PHP has no runtime generics; PHPStan generics are exactly for this. For most cases list<Order> docblocks + strict PHPStan is enough. Write a single generic Collection<T> only when you need behavior.
"Broader impact" isn't bigger features; it's your influence reaching beyond the code you personally write, into the team and the systems. Own one ambiguous, unowned problem end to end.
One rule: if this line fires at 3am, does someone need to wake up? If yes ERROR, if no WARN. ERROR is a promise you broke; wire alerts to ERROR only.
In Kubernetes, probes own readiness/liveness; the kubelet ignores the Dockerfile HEALTHCHECK by design. But keep a HEALTHCHECK for Compose/plain Docker, and point both at the same endpoint.
Never silently remove an endpoint paying partners use. Run an announced, dated, measured sunset: communicate, signal in the response headers, watch usage drop to zero, then remove.
If the same query gets a different plan, the planner's cost estimate differs. On a heavily-written sessions table the cause is almost always stale statistics + table bloat, not a missing index.
A steadily climbing goroutine count = goroutines blocked forever on a channel/lock/IO with no cancellation path. Take a pprof dump first, then make the spawn site honor context.