Everyone reads your config. This one writes it back.
A configuration module that writes changes back without wrecking the file a person wrote, with one small adapter per format and backend.
Tags
76 pages
Go
Which CLI library should you start with?
Choosing a CLI library in Go and Rust. Go is a ladder you climb from the standard library; Rust asks a different question much earlier.
Why my photo app won't build for Windows
Dropping the Windows build of a photo tool rather than fixing it, and why that is the right call for a one-person project.
You can't reshoot a wedding
A photo tool that is non-destructive by construction rather than by intention, because the shoot it works on can never be taken again.
Release trust without the framework
Two new public modules extracting the OpenPGP signing and verification model, so you can use it without adopting the whole framework.
I filed a feature request into my own framework
Building on your own framework means finding its gaps as a user rather than an author, and having to file the request against yourself.
There's no AI in my photo culler
A wedding photo culler that contains no machine learning at all, by deliberate choice. Blur, exposure and eyes, done with plain arithmetic.
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.
Introducing afmpeg and ffmpeg-wasi: FFmpeg with no install, no CGO, no disk
FFmpeg in pure Go with no install, no CGO and no disk: a WebAssembly build running over an in-memory filesystem, and why it exists.
The agent said SUCCESS. The linter disagreed.
An AI repair agent declared success the moment the code compiled. The linter disagreed, and the gap between those two is the whole story.
