| Personal Site | https://thomascannon.me |
| Github | https://github.com/tcannonfodder |
| Bandcamp | https://tcannonfodder.bandcamp.com |
| Practical Computer | https://practical.computer |
| Personal Site | https://thomascannon.me |
| Github | https://github.com/tcannonfodder |
| Bandcamp | https://tcannonfodder.bandcamp.com |
| Practical Computer | https://practical.computer |
A truly amazing gift that my dad made; a 3D woodcut of the Practical Computer logo. And the color matching is perfect too!
It deserves to be right under @jennyrjohnsonart.bsky.social’s amazing work. http://jennyrjohnsonart.bsky.social
I feel like people who are using LLMs for their work are not considering the motives and impact of the corporations hosting and serving the model. The goal isn't to make you a better developer, or even a more productive developer, its to make you dependent on their service and start driving up the rents to access it.
The goal is to extract your time, your money, and your knowledge feeding these models your plans for the work you want to achieve. They are not benevolent.
If you're using `puma-dev` (having `.test` domains and automatic HTTPS is super nice!) but want HTTP2+ support + all the benefits of caddy, I've started work on a small script/setup that provides a `puma-dev` like experience, but using `caddy`!
And best of all, there are no intermediary steps/tools, it's just a setup that strings together 2 out-of-the-box programs.
Every non-hype defense of #LLMs starts with "you must already understand your work really well." But the people vibe coding prototypes *don't*.
As a result they scale up thoughtlessness. "Bulking out" a slapdash idea with hallucinated details only displaces the real thinking that could have led to actual innovation. The very teams the tool was supposed to help instead end up with more noise to dig through.
But teams can (and do) fight back.
If you're using `puma-dev` (having `.test` domains and automatic HTTPS is super nice!) but want HTTP2+ support + all the benefits of caddy, I've started work on a small script/setup that provides a `puma-dev` like experience, but using `caddy`!
And best of all, there are no intermediary steps/tools, it's just a setup that strings together 2 out-of-the-box programs.
I wrote a blog post about why we in the photography space *still* complain about Apple's Aperture going away over a decade later.
It was a *really* good app.
New blog post: A Lament For Aperture, The App We'll Never Get Over Losing
https://ikennd.ac/blog/2026/01/old-man-yells-at-modern-software-design/

I'm an old Mac-head at heart, and I've been using Macs since the mid 1990s (the first Mac I used was an LC II with System 7.1 installed on it). I don't tend to think that the computing experience was better in the olden days — sure, there's a thing to be said about the simplicity of older software, but most of my fondness for those days is nostalgia. An exception to that, however, is Apple's Aperture.