I built a new embedded search engine for browsers that can do both lexical search, vector search, and aggregations. The documentation site for this is powered by this. You can ask questions of the documentation, play with faceting, etc.

https://querylight.tryformation.com

https://gist.github.com/jillesvangurp/56b66cbfd35c33d622948302f98538ed

I had to create a presentation in a hurry. I like reveal.js for this because I can let Codex do the heavy lifting.One issue with reveal.js is that the layout can get messed up when exporting PDFs.

I made codex work around that by just running the slides in a headless browser and taking screenshots. Looks great and good enough to email.

If you want to replicate that, use the gist here. Or just ask your AI coding agent of choice to adapt the script for you.

I’ve been using Codex heavily for months now, and one of the places where it has made the biggest difference for me is DevOps.

I used it to help migrate our hosting off Google Cloud to Hetzner, modernize Ansible, and handle a rolling Elasticsearch restart the way a careful ops person would.

I wrote up what that was like here:

https://dev.to/jillesvangurp/escaping-devops-hell-with-codex-5ap7

Spending a lot of time in the codex desktop app the last few days. Getting a lot of shit done. Loving the interactive planning mode that is turning my brain farts into coherent plans. It asks questions to nail down a good plan. And then it executes that.

This no longer feels like just vibe coding. With the right guard rails, it goes full blown TDD. More anal than the most zealous TDD nerds I've ever worked with. Engineered a few proper things with it in the last few days.

Loving the new codex desktop app. Doing some serious amount of work on our server currently. Scary to see it do lots of work that actually makes sense. My guard rails are working fine so far but they are essential.

I actually came close to running out of context window. But it did complete the job just before that. Need to work on using sub tasks for running tests.

Made the switch from gitx (which I've been using since 2010 or so) to lazygit. Amazing little tool. Great for reviewing diffs and committing stuff in Git. Gitx was always a bit obscure but lately it seems to be getting slower and flakier. It was fine for what it did but just too many freezes / crashes lately.

Lazygit is pretty amazing once you figure out the keybindings (most of which it helpfully displays). Aliased it to gitx to deal with my musle memory issues. Also added the gg alias.

Spending an hour on straightening out the age old problem of "put this ffing thing over there" with Github actions and Google cloud.

You can't test gh actions locally so it's basically me hitting every permutation of possible problems until it somehow works and committing things like "maybe this will work", "yaml syntax fix", etc.

Devops is 95% doing absolutely mundane time wasting shit like that. Just micromanaging a file copy here. Why do the tools suck balls?