looks like a cool place to start
Any conversation
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
A thing I've been doing lately is trying to come to the same conclusions others have without looking their the direct techniques and code. Last night I tried to figure out why people do vector based retrieval for RAG and ended up running these experiments: n0tls.com/โฆ/2026-09-03-i-think-โฆrag-with-grep.html
I'm still going to do an explore agent.
Putting a slide deck together (outside of work), despite agreeing with Tufte on this matter. Iโll also create a handout that tells the story better than the slides and deliver that, too, but was asked to produce a slide deck, and I think thatโs part of the โeffort theater.โ
Using Beamer for the slides, but not a theme that looks like Beamer because humans have eyes.
An interesting thought: historically, a major consideration for companies choosing what to use is how many engineers use it (because that will make hiring much easier/harder). Going forward, this becomes "how big of a corpus of this code is out there", because it impacts how proficient are likely to be at using it.
Gave this evergarden colorscheme a shot after seeing it on lobsters today. Quite liking it.
I have something that usually builds, tests, and deploys under five minutes. It has been over two hours and forty eight minutes and it is still going on today... ๐ซฃ