Go code — CLIs, libraries, compilers, and the naming conventions that hold it all together. Opinionated takes on a language that rewards restraint.
Four months ago I asked ChatGPT a dumb question while walking my dog. It told me building a programming language wasn’t that hard. So I built one — a compiled language with explicit error handling, generics, structured concurrency, and a garbage collector. Here’s what happened.
Why I built mokapot — a single Go binary that speaks SQS and SNS well enough for real AWS SDKs to connect without configuration changes. Persistence, filter policies, and the tricky parts of faking a cloud service locally.
Four real examples from recent Go CLI projects — bracketed paste handling, a scripting DSL, safe symlink restoration, and diff truncation — that show how small decisions separate a script from a tool people trust.
What happens when you give an AI coding agent memory that persists across tasks? It stops repeating the same mistakes. Here’s how lgtm and snap use persistent findings, shared context, and self-recovery to close the loop from planning to merged PR.
Frustrated with complex spinner libraries for your CLI apps? Meet pin—a lightweight, customizable, and dependency-free spinner built with only Go’s standard library, designed to keep your terminal outputs clean and efficient.
Discover why using modern UI frameworks for simple CLI tasks in Go can lead to unnecessary complexity. Learn about choosing the right tools for CLI development and the importance of matching solutions to problems.
Go 1.22 introduces built-in support for iterators, providing a memory-efficient and composable way to handle data streams. This post explains how to use these iterators in CLI applications, complete with code examples and best practices.
A guide to Go naming conventions for functions and variables. Covers best practices for clarity, consistency, and idiomatic Go code to improve readability and maintainability.
