I build tools for projects (MVPs), engineers, and creators.
Mostly terminal-native. Always free, always reversible.
Shellcraft newsletter · @kamon · Content Gardening Studio
I build tools for people who are actually shipping things — founders getting an MVP off the ground, engineers maintaining their own stack, creators publishing on their own terms. The tools tend to be terminal-native (CLIs, build systems, content publishing pipelines) because that's where the leverage is.
I also write about the tools, mostly through Shellcraft (a weekly newsletter going deep on one CLI tool or workflow at a time) and free technical PDFs. The two feed each other: I write a tool, document it, learn from reader feedback, rewrite the tool, repeat.
Currently shipping:
- UV First — The Foundation — a 30-page book that walks through
setting up a Python project with
uvfrom scratch. Free PDF, also available in French. Part of the Python Baselines line. - Python Baselines — a 49-page collected book covering the six patterns every Python project ends up needing: code change, code quality, dependencies, testing, configuration, runtime behavior. Free PDF.
- Shellcraft — weekly newsletter, Tuesdays, one tool or workflow per issue.
| Title | Publisher | Year |
|---|---|---|
| Mastering Python Design Patterns (3rd edition) | Packt | 2024 |
| Learn Type-Driven Development | Packt | 2019 |
| Title | Type | Year |
|---|---|---|
| The Modern CLI Stack | Free PDF (Gumroad) | 2026 |
The Modern CLI Stack is a curated set of 13 terminal tools that replace hundreds of lines of bash config. The PDF walks through each tool with install commands, before/after examples, and a config snippet. The build system behind it is open source and forkable for anyone publishing their own technical PDFs.
Most of my current team work lives under ContentGardeningStudio on GitHub — that's the org for the company I run, and it's where new repos go. A few smaller personal projects still live here on my personal account (mostly older shell scripts, automation notes, and small tools).
- The best tool is the one you actually use. The second-best is the one you'll install and never open. A lot of my writing is about closing that gap.
- Reversibility matters more than cleverness. Every tool I recommend can be uninstalled. Every workflow can be undone.
- Documentation is part of the product. If a tool needs a forum thread to be usable, it's not done.
- I keep my hands on the keyboard. Mouse-driven workflows are fine for the first minute of a task; after that, they're friction.
- Newsletter — Shellcraft (Tuesdays, one tool or workflow per issue)
- Microblog / quick takes — @kamon on X
- Studio — Content Gardening Studio (the company I run; longer-form work and consulting)
This is a GitHub profile README — the page you're reading right now is rendered from a README.md in a special repository called kamon/kamon. If you want to see how it's set up, the repo is public.
Last updated July 2026.