The cleanup tool that almost deleted its own hands
Reading an aws-nuke dry run: the screenfuls of red are harmless noise, and the real hazard is one quiet line in the middle of them.
Categories
121 pages
Pioneering
Notes from active builds: the design decisions, war stories and how-it-works of whatever I'm making right now.
The security finding you must not fix
A checkov finding you must suppress rather than fix: that KMS policy statement is the escape hatch that stops you locking yourself out for good.
Two telemetry events, one mangled line
O_APPEND only guarantees non-interleaved writes below PIPE_BUF, which is 4096 bytes on Linux. A fat JSONL event above that splices two lines.
A state bucket that defends itself
An OpenTofu state bucket that defends itself against corruption, deletion and its own operator, using lockfiles and prevent_destroy.
Supporting a provider, or actually using it
A lowest-common-denominator AI interface throws away what each provider is good at. When to route through an abstraction and when to drop below it.
Errors without an error handler
Go funnels errors through a handler. In Rust, diagnostics carry their own code and help and propagate on their own, so the funnel disappears.
The bootstrap that does almost nothing
An AWS bootstrap module that does exactly three things, and writes down what it deliberately does not do. Scope as a design decision.
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.
forbid means forbid, until linkme needs a word
forbid(unsafe_code) is absolute, which is a problem when a dependency emits a link_section the lint counts as unsafe. Where the line ends up.
A framework that contains no unsafe
Why every shipping crate uses forbid(unsafe_code) rather than deny, which any module inside it can quietly override from the inside.
