I build Rails systems and take responsibility for what they do in production. At GitHub I helped ship the billing infrastructure behind Copilot subscriptions. Most of my opinions below come from cleaning up after quiet bugs.
Lately I've been building tools for AI coding agents working in Rails codebases.
- Building static-analysis and context tooling so agents get facts about a Rails codebase instead of guesses
- Testing AI coding agents against real production workflows and keeping notes on what holds up
- Deepening my Go and distributed systems experience to complement my Rails work
- π Big picture first. I want the architecture and the business reason before I touch code. If I can't draw it, I don't understand it yet.
- π Find the loop, not the event. Recurring problems have a structure producing them. I fix the structure.
- β±οΈ Tight feedback loops beat capacity. Anything I automate has to say how we'll know it's working, and how fast.
- βοΈ Less code by default. Abstraction has to earn its place with about three real uses first.
- π§ββοΈ Agents write code, I design the system. They get the decision-free work. Architecture, schemas, and dependencies stay with me.
- π Trust is the foundation: teams work when people feel safe
- π Self expression matters β that's why I love emojis
I train jiu jitsu π₯ and study markets π.
- π« fuentesjr@duck.com
- π linkedin.com/in/fuentesjr