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.
Any conversation
there's no fundamental physical limit that prevents silicon from developing taste and judgement, but language is a lossy compression of reality.
taste comes from experience, from the shadowy mass of episodic memory, which swirls and convects at the boundary of consciousness. the ideas recombine into new ones in the nuclear reactor of the hippocampus.
but no matter how imbued with meaning and expertise is a handmade wardrobe we still get our shit from ikea
Drew a comic of vulpes inculta and my oc, I love SO MUCH!!
ibb.co/B2x8dq9n
Having spent the last 12 months using HTMX in $day_job, after 5 years with react, I have come to the opinion that whilst large amounts of JS and CSS are not necessarily wrong, they should be reserved for progressively extending the platform with a composable set of generic UI primitives that build out a cohesive design language โ encoding business logic (including routing) there is generally a mistake
I needed to process 20,000 json files & 20,000 JXL files. I'm pulling together a website from them all. Anyway, started with emacs elisp to handle it all, just because I've not done that before. Went kinda ok, and I'm gonna use org-mode to export it all to a website (done that bit loads of times before).
In the end, I ended up breaking out my C programming skills (late 80s->nowish). It was a delight. Nothing more refreshing than writing raw code, that doesn't rely on 3rd party code/libs.

