go
01
2026-10-27
i don't vibe code. i build fences.
↵ open
02
2026-09-29a schema per era: modelling eighty years of race results
↵ open
03
2026-09-15four endpoints, eight megabytes each, and a stranger with a for loop
↵ open
04
2026-08-18never let the client tell you who owns it
↵ open
05
2026-07-08verifactu in go: a sha-256 hash chain is spain's answer to invoice fraud
↵ open
06
2026-03-16i didn't leave go for rust. i split my stack.
↵ open
07
2025-12-29i audited my side project like it was about to go viral (before it was)
↵ open
08
2025-12-22your rate limiter trusts x-forwarded-for. mine did too, until it was measured.
↵ open
09
2025-11-24sqlc + pgx over an orm: type-safe sql that fails at compile time
↵ open
10
2025-03-08testcontainers 103
↵ open