baweaver

Transactions are more complicated than an easy-to-use block, and treating them as such will come back to bite you.

How I process problems: hyperphantasia, rotation, the click moment, and using AI as a variance accelerator for a brain that generates more ideas than it can hold.

Organizations teach themselves helplessness through reinforcing loops of scarcity, cynicism, and declining trust.

For those who don't know me, I'm autistic.

A walkthrough of my current development environment: Ghostty, MonoLisa, mise, ZSH without a framework, and why I automated the whole thing into a single script.

I need to level up on Go, and Pokémon data felt like a good excuse.

Checking whether you've seen something before usually means storing everything you've seen.

You inherited a monolith with no map.

Every successful Rails monolith becomes a ruin if it survives long enough.

Polymorphic associations store a relationship as a class name in a string with no foreign key.

Counting distinct values exactly means remembering all of them.

Queries own the reads the way commands own the writes, and a T::Struct is the only thing that crosses between them.

Callbacks promise that something always happens when a record changes.

add_index looks like a one-line fix for slow queries.

Enumerable assumes the whole collection fits in memory.

Enumerable named the ways we walk a line, but some data is not a line.

Enumerable named our traversals, but some collections live past it.

lock looks like a one-line fix for concurrency bugs.

Enumerable taught us a better path for iteration, what if we applied those lessons to other forms of iteration?

Every guardrail we need for AI is a good practice we should have already been doing.