All Tags

Migrating from Ghost to Hugo using Claude

Sunday, Apr 5, 2026

Decided to move my blogs from Ghost to using Hugo and generate a static website for the content. The reason for this was I don’t use all the fancy features of Ghost. I don’t do newsletters and Ghost requires an email account if people want to sign up for notifications. Plus I have to run a database for the content.

I started with creating an new directory and fired up Claude and started with this initial prompt.

Coding with Claude AI

Wednesday, Jan 21, 2026

So I wanted to see what AI coding can do and started claude with /plan

Make a clone of Bejeweled game to run on Linux

It laid out the requirements, made a to-do list and suggested Rust + bevy for the implementation. I agreed. It asked would you like me to build it and off we go.

Initial commit didn’t have tests, executed but the grid for the gems was offset. I looked at the code and figure the something was a miss with the layout and asked Claude

LazyVim setup for NeoTest and Native Node.js Test Runner

Sunday, Dec 28, 2025

The simplest and most effective approach involves using the devastion/neotest-node plugin. Create a configuration file at ~/.config/nvim/lua/plugins/neotest-node.lua

Configuration

return {
  "nvim-neotest/neotest",
  dependencies = {
    "nvim-neotest/nvim-nio",
    "nvim-lua/plenary.nvim",
    "nvim-treesitter/nvim-treesitter",
    "devastion/neotest-node",
  },
  config = function()
    require("neotest").setup({
      adapters = {
        require("neotest-node"),
      },
    })
  end,
}

The configuration specifies neotest as the core framework with neotest-node as the adapter for Node.js test execution. All required dependencies are declared and initialized during plugin setup.

NeoVim AI Coding Assistant w/Avante

Sunday, Dec 14, 2025

Initial Setup & Claude Integration

The author explored integrated AI coding assistance within NeoVim using Avante, recognizing that vague prompts produce problematic outputs. After testing Gemini 3’s limitations with broad requirements, they configured Avante with claude-sonnet-4-20250514.

When tasked with generating tests for a registration route, the assistant “created a task list of 8 things to plow through and chugged on that for 5 minutes.” Test generation cost approximately $1.04. The assistant also refactored monolithic code, separating functionality into distinct files.

AMDGPU Ring Timeout / Minecraft Workaround Using Mesa Zink

Tuesday, Sep 23, 2025

Main Problem & Solution

The author describes encountering AMDGPU ring timeout issues with Minecraft on an AMD Radeon RX 6700 system. Rather than modifying kernel parameters, the solution involves leveraging Mesa’s Zink driver—a compatibility layer translating OpenGL calls to Vulkan.

Hardware Configuration

• CPU: Intel Core i5-12400F
• GPU: AMD Radeon RX 6700 (Navi 22, RDNA-2)
• OS: EndeavourOS (Arch-based distribution)
• Desktop: KDE Plasma (initially), later tested Cosmic and Hyprland
• Display: Dual 4K monitors with Freesync support

Initial Setup

Required packages:

LazyVim + neotest-mocha and overcoming "No test found"

Sunday, Sep 7, 2025

Overview

The author transitioned from AstroVim to LazyVim and configured neotest-mocha for test running in NeoVim. The setup required careful attention to file discovery patterns.

Installation Steps

Mason Tools Installed

• bash-language-server
• eslint_d
• gitui
• js-debug-adapter
• lua-language-server
• marksman
• prettierd
• shellcheck, shfmt
• sqlfluff
• stylua
• typescript-language-server
• vtsls

Lazy Extras Loaded

• dap.core, dap.nlua
• editor.inc-rename, editor.neo-tree
• formatting.prettier
• linting.eslint
• lsp.none-ls
• test.core
• util.gitui, vscode

Configuration

A plugin configuration file was created at ~/.config/nvim/lua/plugins/neotest with neotest-mocha adapter setup. The config includes custom command arguments handling context data for test execution.

Linux amdgpu: ring gfx_0.0.0 timeout

Thursday, Sep 4, 2025

Running Wayland and experiencing Minecraft issues with kernel 6.16.3-arch1-1. GPU timeout errors appeared in system logs indicating the graphics processor failed to complete tasks within expected timeframe.

Initial Problem

Kernel logs showed: ring gfx_0.0.0 timeout, signaled seq=7925632, emitted seq=7925634 with the graphics device requiring a complete reset to recover.

Hardware Configuration:

• AMD Radeon RX 6700 (Navi 22)
• 12th Gen Intel Core i5-12400F
• 64GB RAM
• KDE Plasma 6.4.4 on Wayland

Troubleshooting Process

The author identified a Mesa regression by running glmark2 benchmarks, which initially crashed the system.