Fluffy and Flakey

HTML and XML are markup languages based on plaintext files.

Last week at WordCamp Europe there was a get-together among WordPress Core committers and a question arose concerning the separate Gutenberg npm packages that are built and distributed.

This is a wildly helpful trick: I want to see all the revisions in which a particular line of code changed.

My mind may be playing games on me, but I feel like I’ve witnessed signs of crumbling software over the past few months.

Today someone was discussing the goal of linting HTML, specifically of detecting unclosed attributes.

This probably isn’t original, but I am declaring that a “slop in the face” is when someone returns a well-considered, thought-out, intentional interaction by pasting in an LLM-generated response, meeting care and diligence with contempt and disregard.

Frequently I want to compare a given git branch or other ref against its “target branch” because I’m reviewing a PR.

A number of people have asked me about ways I use git and “stacked branches,” where in-development work depends on other in-development work.

A while ago I wrote about Rooting out Gremlins on text which was corrupted in a common way by accidentally double-encoding UTF-8.

The companies providing LLM services are built upon foundational conflicts of interest.