Writing

Whisper's turbo model beat large on noisy audio, in practice

Composite index column order should match the query, not the schema

Daemon threads for WebSocket keepalives

Give callers two error types, one extending the other

A single catch-all exception forces every call site to over-handle. Two types in a hierarchy let each caller pick its own granularity.

Two-sided membership needs one lock, not two

A bidirectional relationship (users know their rooms, rooms know their users) has to be updated under a single lock, or readers will catch it half-done.

Generic returns can be the right call for a library you maintain alone

Typed response structs are the default advice. For a one-person library wrapping a churny upstream API, `(any, error)` was the cheaper long-term choice.

Endpoint maps over hand-rolled methods

When a client library wraps ~25 near-identical HTTP endpoints, describing them as data instead of writing 25 methods pays off, with one real trade-off.