Blog on cephei8's site

Neovim setup for Odin

Thu, 14 May 2026 00:00:00 +0000

Recently I have been experimenting with Neovim.
This post is about how to set it up for Odin programming.

I will cover:

syntax highlighting
building/testing/formatting Odin code from Neovim
LSP
autocomplete
debugging

Prerequisites

Install Odin
Install ols and odinfmt (LSP + formatting)
Install tree-sitter-cli (for installing Odin Tree-sitter grammar)
Install latest llvm and make sure lldb-dap is accessible (for debugging)
Set up lazy.nvim

Syntax highlighting

I recommend using Tree-sitter for syntax highlighting.

My Large Array of Things in Odin

Sun, 05 Apr 2026 00:00:00 +0000

Background

If you are not familiar with the concept of Large Array of Things, I highly recommend watching Avoiding Modern C++ | Anton Mikhailov on Wookash Podcast, both for educational purposes and for inspiration.
In two words - it’s an array of fat structs, with intrusive data structures to implement hierarchies.

In this post I will show my implementation of the concept in Odin, demonstrating some nice features that Odin has to offer. Particularly:

Doom Emacs setup for Odin

Sun, 08 Feb 2026 00:00:00 +0000

Doom Emacs, as expected, can be made into great “IDE” for Odin.

This post will cover setting up syntax highlighting, LSP, build command, and debugger.

Syntax highlighting

Odin Tree-sitter mode provides a nice syntax highlighting.

Add the following to packages.el:

;; packages.el

(package! odin-ts-mode
 :recipe (:host github :repo "Sampie159/odin-ts-mode"))

And config.el:

;; config.el

(use-package! odin-ts-mode
 :mode "\\.odin\\'")

Odin Tree-sitter grammar needs to be installed separately.

Add the following to config.el:

Making user-facing DSL with goyacc

Mon, 02 Feb 2026 00:00:00 +0000

One of the core features of my Greener project is user-facing DSL for querying database with test results.
For example, status = "fail" AND name = "login_test" fetches results of the “login_test” test that failed.

Surprisingly, Go’s port of classic YACC parser generator was a relatively simple and straightforward way to parse user queries to further convert them in SQL queries.

Note: this post covers a very simplified approach for educational purposes.

Go's Bun ORM - alternative to Python's SQLAlchemy

Fri, 02 Jan 2026 00:00:00 +0000

Initially, my Greener project was implemented in Python.
When I decided to switch to Go, I started looking for Go ORM library. In Python the de facto standard is SQLAlchemy. I liked SQLAlchemy and was hoping to find something similar for Go.

Specifically, I was looking for the following:

Actively maintained
Support for different databases (in the sense that same code works with different databases)
ORM layer (for simple queries)
SQL eDSL (for complex queries)
Support for dynamic queries (e.g. variable set of query conditions etc.)
Migration system

I settled on Bun - while not being as ergonomic as SQLAlchemy (not Bun’s fault, I think it’s done a great job given the programming language) and not ticking all the boxes, it still covered the most important parts.

Greener: lean and mean test result explorer

Tue, 25 Nov 2025 00:00:00 +0000

Test frameworks usually produce custom test output by default (along with exit code).
For example, pytest (test framework for Python) gives something like this:

tests/test_apikey_controller.py::test_create[db_sqlite] PASSED [ 25%]
tests/test_apikey_controller.py::test_get[db_sqlite] PASSED [ 50%]
tests/test_apikey_controller.py::test_list[db_sqlite] PASSED [ 75%]
tests/test_apikey_controller.py::test_delete[db_sqlite] PASSED [100%]

This is fine if a number of tests is small, or we mostly care about overall test result - if all the tests in the test session passed.

However, once we need to investigate test failure, especially for larger/longer test sessions (e.g. end-to-end tests), often the following questions need answers: