go

Your authorisation layer is correct and your query still leaks

A permission check answers "may this user do this". It doesn't answer "to which rows". In multi-tenant software the second question is the one that leaks data, and it fails in a way that passes every test you've written.

gosecuritymulti-tenancypostgres

The third consent state nobody builds

Consent banners give you two states and the law has three. Here's a cookieless measurement mode for visitors who haven't decided yet, why Article 5(3) isn't engaged by it, and how to prove your own tracking works when you cannot see it from your own network.

privacyanalyticsgdprgo

Handing the easy tickets to a free local model cost 1.65x more

I built a harness to grind the mechanical backlog tail on a local Ollama model and measured what it actually saved. Across three real tickets the local-model path cost 1.65x the Claude tokens of just doing the work, and every output needed fixing before it could merge.

agentstoolingprocessgo

A library-centric Go monorepo, and the one rule that makes it work

38 shared libraries across 75 modules and a dozen production apps, run by one person. The thing that makes it survivable isn't the tooling - it's a rule about where a fix is allowed to go, and a worked example of paying it.

gomonorepoarchitecture

Why your OpenTelemetry build broke, and how to check the whole set

OpenTelemetry ships as several modules with different version numbers that are all one release. Go has no idea. Here is how to tell which versions belong together, why it breaks, and a check you can run in CI today.

goopentelemetrydependencies