Classics are classics for a reason, right? Such a beautiful movie! And feels really good to watch, too. The scenes just flow with such levity and you don’t even feel the time pass.

beyond tellerrand is the affordable single-track event where creativity and technology meet. Taking place in Düsseldorf and Berlin these days with 500+ attendees each in a renowned, familiar and friendly atmosphere.

A short and easy to read book that actually has a surprising amount of depth. While it took a while for me to get invested in it, once I did it really left a mark.

An absolute nothing burger of a film. An ET movie in 2026 ought to try to do something new or different, but this one does nothing. It takes itself so seriously that it just feels silly. It’s even sillier how many shots there are of people reacting to how serious the things happening in the movie are, as if the movie is trying really hard to make you care, too. I didn’t.

Millions of _Large-Language-Model_ -generated words have been spilled on craftsmanship in this **gilded-age of software development**. We now have agents to plan how code will be written, agents to write code, agents to review code, agents to orchestrate and dispatch tasks to other more (or less) capable subagents (these heavily subsidized tokens aren’t going to pay for themselves). I’ve been in this game long enough to recognize tooling improvements from software companies at the bleeding edge of technique and application and it usually goes something like this: “If we make it easier for developers to create software, they will have more bandwidth to produce higher quality software!” I’m always left wondering (suspecting the answer with hopeful optimism that my hunch is wrong this time): do these workflow improvements actually improve how people (technical or otherwise) _experience_ software? Certainly **we have more software**. But is it better? I don’t know. Front-end web developers have lived through a few cycles of this (seven or eight years of client rendering, fifteen years of the _single-page-application_ -era smokescreen are a few that come to mind), sold as though improvements to developer experience would cause the reanimated corpse of Ronald Reagan himself to ask you for commit access to ship trickle-down improvements to user experience. Is this cycle repeating the same playbook (on a more accelerated pace)? Certainly we’ve seen numerous recent anecdotal examples of software becoming _less_ reliable over time (GitHub is the most recent scapegoat I’ve seen, but on my read they seem to be a second-order victim more than anything). _(Seems like a great time to be in the Monitoring/Status Page business)_ With these seismic changes, I will continue to make the argument that craft defined as **caring about the quality of output** (independent of the tools used to generate the output) is **more important than ever**. Caring about what you ship will always have **real-world value** to ~~visitors/consumers/users~~ **real people**. _Prefers-reduced-motion respecting web performance filmstrips fromthe AI category on Speedlify, a category boasting a failing median Core Web Vitals score with 12 out of 13 sites failing Lighthouse performance and Axe accessibility checks._

One pixel – one personal blog. Explore the field with your lantern: no metrics, no algorithms, everyone equal.

Possible knowledge gap on my part, but cool nonetheless: the form attribute allows your form controls to live anywhere.

Possible knowledge gap on my part, but cool nonetheless: the form attribute allows your form controls to live anywhere.