I'm a senior software engineer who builds with AI coding agents every day. I think they're the biggest change in software engineering, and I'm all in on guiding these agents to build ambitious software.
My depth is 15 years of production backend work, mostly Ruby on Rails. At GitHub I helped ship the billing infrastructure behind Copilot subscriptions. That experience is what I bring to agent work: I know what a production system needs, so I can move fast in whatever language the problem calls for and still ship things that hold up.
- Building tools that give coding agents facts about a codebase instead of guesses
- Going deep on web application security. As agents write more of the code, I want to be the engineer who can tell when it's exploitable.
Agent workflows
| Project | What it does | Built in |
|---|---|---|
| sbx-orb-provider | Self-hosts the Amp coding agent's cloud workspaces on my Linux box: one microVM per agent, default-deny network, and a daily canary that checks for drift (walkthrough) | Shell |
| autobots Β· agenticons | Named subagent rosters for Claude Code and Codex, each role pinned to a model tier | TypeScript, Go |
| grok-plugin-cc | Claude Code plugin that hands investigation, fixes, and review to Grok Build | JavaScript |
Codebase understanding
| Project | What it does | Built in |
|---|---|---|
| c4lens | Desktop app and CLI for navigating C4 architecture models stored in a repo | Rust, React |
| git-recon | History-first codebase investigation for humans and agents | Shell |
| metz-scan | Finds Sandi Metz-style design pressure in Ruby and Rails code | Ruby |
Web AppSec
| Project | What it does | Built in |
|---|---|---|
| rails-audit | Rails static analysis: pinned brakeman, rubocop, and reek, ranked by impact | Ruby |
| bobby-tables | Interactive guide to SQL injection and parameterized queries (live) | HTML, JS |
- π 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.
- π§β
βοΈ I guide the agents and own the design. Agents do the implementation at speed. 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