Because of spammers, I am going to have to now redo how my family sends/receives email at my custom domain. Too many folks required DKIM now for me to be able to use Send As on Gmail without using a custom SMTP server that can handle signing, or paying for a Google Workspace (which I don't want to do). Sartre was right about Hell.

I got two AI agents, Claude and Gemini, to help generate a doc for new developers on how to work with one of our services. In the end, I am quite pleased with what it did.

Example:
# Developer's Guide to the User-Profile Service

Welcome! This document is the comprehensive guide for developers working on the
User-Profile service. It outlines our architecture, established patterns, and
development workflow. Adhering to these conventions is key to maintaining a
clean, consistent, and scalable codebase.

## Table of Contents

1.  [**Getting Started: Your First 5 Minutes**](#getting-started-your-first-5-minutes)
2.  [**Core Architectural Principles**](#core-architectural-principles)
3.  [**Codebase Tour**](#codebase-tour)
4.  [**Quick Decision Guides**](#quick-decision-guides)
5.  [**The Golden Path: Adding a New Feature**](#the-golden-path-adding-a-new-feature)
6.  [**Deep Dive: Key Patterns & Conventions**](#deep-dive-key-patterns--conventions)
    - [The Data Layer (`stores/`)](#the-data-layer-stores)
    - [Event Handling (`event_consumer/`)](#event-handling-event_consumer)
    - [Command Handling (`command_consumer/`)](#command-handling-command_consumer)
    - [The API Layer (`webapi/`)](#the-api-layer-webapi)
    - [Error Handling Patterns](#error-handling-patterns)
    - [Testing (`*_test.go`)](#testing-_testgo)
    - [Long-Running Tasks (`temporal/`)](#long-running-tasks-temporal)
    - [Observability Best Practices](#observability-best-practices)
    - [Configuration Management](#configuration-management)
    - [Performance Considerations](#performance-considerations)
    - [Cross-Cutting Concerns](#cross-cutting-concerns)
7.  [**Development Cheatsheet**](#development-cheatsheet)
8.  [**Glossary of Terms**](#glossary-of-terms)

We've been fairly effective at getting Claude Code to write useful code on our repos. I say useful, in that it saves some time. Not in that it's ready to ship.  However, this seems to be in a large part because we have a lot of patterns that are supportive of human developers as well:

• Good README in each repo
• Makefiles (with help) in each repo that make it easy to work with the service locally
• All service defaults work in dev so locally you don't have to specify any configuration
• Docker builds and all deps running in `docker-compose` so you can stand a service up locally
• Shared patterns between repos that are enforced (e.g. same libs, same DBs, etc)
• Shared protobuf schemas used by all services
• Extracted libraries with common code
• Standardized testing framework
• 80+% test coverage on Go repos, higher on Elixir repos where type safety doesn't help as much
• A system-wide YAML file describing each service, what it depends on, what it produces and consumes

All of the above makes it easy to work on our codebases for humans. And it makes AI much less likely to go off script and make a mess.

I finally published the blog post I was working on about how we wrote a C Node in #CrystalLang to call into our existing #Golang libraries from #ElixirLang! You can read about it here: https://relistan.com/calling-go-from-elixir-with-a-cnode

I'm having a weird #Golang dependency issue that I've never seen before. The code compiles on macOS and Alpine Linux absolutely fine. On Ubuntu and Debian I get a complaint from the compiler that the dependencies need to have `go mod tidy` run. Running it does nothing.

This stinks... because our CI is Debian. Very strange issue.

I shipped an app some months back that uses Badger (#Golang) as the data store. I wanted to be able to see what was in the store easily when debugging, so I stuck a simple Redis API into the app using redeo as a local-only port. I exposed a few Redis commands to make it easy to see what was in the store, walk keys by prefix, etc. This took maybe 1.5 hours to add. It has been super useful. I think I'll do this again next time I ship something with Badger.