- Powered by
- WordPress
-
[dedo] 8: Dedo Breaking Rules
buf breaking compares descriptors, never option values, so a removed scope, a moved REST path or a renamed event type passes it. dedo v0.32.2 adds ten breaking rules for what Buf cannot see, and lets you write your own as CEL checks against the version before.
-
What the Go Linker Does
What cmd/link does at the end of every go build, when linking actually happens, and why anything passed to -X can be read by anyone who has the binary.
-
[dedo] 7: Forking dedo (You Probably Don’t Need To)
You almost certainly don’t need to fork dedo: your conventions live in dedo.yaml, and everything you install is already pinned. If your organisation must review every line before it ships, a fork is supported, scripted and pleasantly boring.
-
[dedo] 6: How fast is Dedo?
dedo v0.15.0, measured from scratch: an MCP server in three commands, a house rule in five lines, 338 lint rules in 0.32 s, and 12,718 authenticated MCP tool calls a second on one CPU core, 25,339 on two.
-
[dedo] 4: House Rules, Your Rules as Lint
Every organisation has conventions no public standard knows about. dedo lets you write them as CEL checks in dedo.yaml, share them from one git tag or a pinned URL, and see them in the editor.
-
[dedo] 3: Adding dedo to an Existing Service
dedo installs one layer at a time: annotations, lint, generators, runtime. Each layer pays for itself. Audit before you enforce.
-
[dedo] 2: Getting Started: Todo Good and Todo Bad
Two to-do services with the same interface. One follows every rule. One breaks every rule, and its tests show what each mistake costs at runtime.
-
[dedo] 1: Define Once, Deploy Everywhere
One .proto file can carry an API’s contract and its operational rules. A linter can make good architecture the easy path. This is why I built dedo.
-
Why Is It v1 for a Namespace but apps/v1 for a Deployment?
If you’ve written more than a couple of Kubernetes manifests, you’ve probably copy-pasted these lines without thinking too hard about them: