A stack trace is not an error message
A tool-failure log dumped a wall of Go stack frames where one line would have done. What a log record owes the person reading it.
Tags
7 pages
Engineering
The cobra hook I was sure I'd enabled
An audit found that a Cobra option had never been enabled, so the root command hooks had silently not run on any subcommand for months.
When you hand the same key to every call
A generated nested command would not compile, and the cause was a scaffolder handing every call the same key regardless of depth.
Two kinds of feature flag
Runtime feature flags decide which commands are reachable on a given run. Cargo features decide what is compiled in at all. Do not confuse them.
Reloading config without a restart
Hot-reloading configuration: watch the file, re-read it, swap it in atomically and notify observers, without restarting a long-running service.
What survives a port, and what doesn't
Porting a Go framework to Rust separates design from idiom. Which decisions survived the move, which were habits, and how to tell them apart.
Errors that tell the user what to do next
Recovery advice belongs in a structured error hint, not buried in the message string. One error handler then decides how to show it.
