This is my first note, there are many like it, but this one is mine.
Any conversation
Yesterday I with help from the clanker, as an experiment, ported a web app from go+postgres+svelte to ari+duckdb+htmx served locally by busybox httpd. Itโs an analytics โdashboardโ so the stack makes sense. So far looks good. Now I work on the code in vim to make it mine. I want fewer layers of abstraction and less complexity, and this is a learning experience to that end.
recently, I have fallen in love with the artwork of takato yamamoto.
WARNING FOR NSFW ARTWORK
ibb.co/dJrZjr6C
Things I'm enjoying lately:
Vampire Survivors + Diablo IV
Alien + Dune ambiance
Howling Dark book 2 of Sun Eater
great TV
I find myself building bespoke tooling for my own and workflows these days, not only because of the obvious reason of software being so much cheaper to build, but also because there are SO MANY options for solving any given problem that it feels impossible to evaluate all of them.
If it's not a crucial piece of tech for a work problem then it often feels like paving my own way is both cheaper mentally (kind of amazing that's true these days) and probably a better fit.
azรฉrt aranyos, hogy egybลl sandbox-ba kell tenni (a Virtualbox egy sandbox), hogy szรฉt ne barmoljon mindent a gรฉpen vagy a szerveren, vagy mรกshol, azรฉrt alapvetลen bรฉkรฉs kis รกllatkรกk ezek az ai chatbotok, na
It's cute because you have to put it in a sandbox right away (Virtualbox is a sandbox) so it doesn't mess up everything on the machine or the server or anywhere else, but these AI chatbots are basically peaceful little animals, right?
one-point-five-shotted a local node app for creating social posts. drawing from static pages (hey this exists) or new blog posts (timely). with copy/paste to x, and one click post to bluesky and mastodon, tag manager and stale/archive/reject/refresh options. An idea and a solution in about 10 minutes. Madness.


