1. If you came from Jekyll or Gatsby, you want a git-based CMS

    Why a git-based CMS is the natural successor to Jekyll or Gatsby — your content stays as markdown in the repo, the editor just sits on top. Plus what I found running Decap and Sveltia side-by-side.

  2. My first RAG, part 2: I built generation. One endpoint sang. The other lied about people needing the bathroom.

    Week two of the RAG project — added /summarize and /answer on top of retrieval. /summarize was the surprise hit. /answer had a polite refusal problem and then a stranger one. Notes from the workbench.

  3. My first RAG

    From zero Python service experience and zero RAG knowledge to a working YouTube transcript retrieval pipeline. The mental shifts, the decisions, and the gotchas that surprised me.

  4. Hosting on AWS, cloudfront and ALIAS records (and BAD GoDaddy)

    Hosting on AWS, cloudfront and ALIAS records (and BAD GoDaddy)

  5. Issues with wordpress search

    Wordpress search is not very good. Relevanssi is a very good plugin.

  6. Migrating from Next.js to Astro

    Three years after migrating to Next.js, I migrated off it. Why I left, what the move to Astro looked like, and the numbers from this site's rebuild.

  7. Next js - Is it getting just too hard to use?

    I used to write React.js. It was not easy at the beginning but eventually, I learnt the React's ways and it made alot of sense. I used to use Gatsby, some of the set up was a bit too

  8. Migrating from Gatsby to Next.js

    Reflections from leaving Gatsby for Next.js in early 2023 — what worked, what didn't, and what the migration actually cost.