The release that OOM-killed its own compiler
A wedding-photo culler ran out of memory compiling an LLM SDK it has never once called. The release had been running for thirty-eight minutes at that point.
Tags
9 pages
Photography
Cull a shoot, end to end
Twenty minutes from a folder of frames to an album-ready export, with nothing written over an original. Also: the install method that will cost you an evening if you pick the obvious one.
Ten lines of XML so a cull shows up in Lightroom
A cull is worthless if it cannot follow you into Lightroom. Writing XMP sidecars out of krites, and being careful about what not to write.
The feature your users are already faking
The one real user of my photo tool was already faking a feature with a workaround. That workaround was the specification.
About that 'no AI'...
A correction to my own post: the culler does contain machine learning, and the distinction I drew between ML and AI does not survive scrutiny.
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.
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.
I built my wife a judge
Launching krites, a local-first wedding photo culler built for one photographer who had four thousand frames and a weekend to get through them.
