#Go

A bidirectional relationship — users know their rooms, rooms know their users — has to be updated under a single lock, or readers will catch it half-done.

When a client library wraps ~25 near-identical HTTP endpoints, describing them as data instead of writing 25 methods pays off — with one real trade-off.

Typed response structs are the default advice. For a one-person library wrapping a churny upstream API, `(any, error)` was the cheaper long-term choice.

A thread-safe Go library providing a reusable Room–User architecture for real-time systems like chat and multiplayer games.

A self-hosted URL shortener with a React admin panel, built with Go, Redis, and PostgreSQL.

An open-source unofficial REST API client for the WazirX crypto exchange in Go, acknowledged by WazirX's co-founder.

A Chrome extension for saving, organizing, and listening to notes from any webpage, backed by a Go/Fiber API and a React admin panel.

The canonical Go book — worth a proper read now that Go is my main language.