macOS, close to the metal
Menu-bar utilities that read real hardware state — charger input, display brightness, disk usage — and put the number where you can see it. Swift, AppKit, and a healthy suspicion of vendor defaults.
About
Most of this starts the same way: a device reports something slightly wrong, or a service holds data I'd rather keep, or a workflow has one step too many. So a tool gets written. Then, because it might be useful to someone else, it gets pushed.
Menu-bar utilities that read real hardware state — charger input, display brightness, disk usage — and put the number where you can see it. Swift, AppKit, and a healthy suspicion of vendor defaults.
Services that run on your own hardware and stay private: podcast feeds built from YouTube channels, family archives, and the small servers that keep them going.
Zotero extensions that make AI summarisation explicit and privacy-aware — you bring your own agent, nothing leaves the machine without saying so.
A split-flap display emulator for any television, a browser tweak, a flight-sim METAR translator. Not everything needs a business case.
Every project here is something one person can hold in their head. Small tools get finished, and finished tools get used.
Data stays on the machine that made it. Self-hosted services, no accounts, no telemetry, nothing phoning home.
Numbers should come from the hardware, not from a spec sheet. If a charger claims 140 W, the tool should be able to check.
If it was worth building, it is worth pushing. Every repository here is open, forks included.
Get in touch
Every repository is open. If something here is nearly useful to you, open an issue and say what's missing.