/dev/null
Job Chong

As noted in many places Claude Code and Codex are now harnesses of exceeding quality. Personally I can't bear to use IDEs and plugins and whatnot, so it's been a great pleasure to have an LLM interact with my code in the same tools I use. Perhaps that's the main developer experience value-add for these model harnesses.

I'm (or more accurately, Claude/Codex) are working on harp, which is the start of the equivalent in Emacs. Perhaps my IDE snootiness is hypocrisy given that I'm working on this, but oh well.

Some things I've noticed about both Claude/Codex while observing their output:

• They're incredibly bad at matching parentheses in Lisp. Like five minutes to find a missing/extraneous parenthesis bad. I find this extremely funny, and it reminds me of the r's in strawberry stuff. I'm watching codex run perl -ne multiple times trying to match them.
• Codex is so good at creating a harness for itself I suspect it's been specifically trained to do it.
• /review in Codex is great for spotting security issues and edge/corner cases with malformed user input.

Org-mode complaint: I do wish there were some elegant org-native way to specify links to open in a new tab. Alas, we only have the #+HTML_HEAD global directive, and so most links on here are inline HTML.

I've somehow managed to create a CI issue in a Pages repo, where publish.el doesn't copy over the CNAME to ./public. So every time I push changes I nuke the CNAME in gh-pages, which uses the ./public folder. Wonderful.

Surprisingly Codex didn't catch this issue. Perhaps I didn't describe the Actions stuff clearly enough? In the future I should go through build details with Codex as well when coming up with an implementation plan.

Also GitHub should really only allow you to set the custom domain from the CNAME itself, and remove that field in your Page settings.

Publishing flow:

1. Add or edit Org files under content/ (use subfolders as you like).
2. Run emacs -Q --batch -l org -l ox-publish -l publish.el -f org-publish-all from the repo root.
3. Inspect the generated HTML in public/ and commit if you want to track it locally.

If you prefer to keep the main branch clean, let the GitHub Actions workflow deploy public/ to the gh-pages branch for you.