About

Hi, I’m Fabio! 👋

I’m a software engineer based in Brazil, hacking on developer environment tooling since 2013 - first to make my own setup less painful, then as open source, and most recently as the kind of environment a coding agent can work inside.

My day job is Ruby on Rails and has been for about 15 years, with a brief detour through Golang and Kubernetes somewhere in the middle.

What I’m Writing About

Most of my recent writing is around AI and developer tooling. There’s a series on modernizing my terminal-based dev environment that walks through what my stack looks like in an agentic world. Standalone posts poke at adjacent questions: giving agents a mailbox so they can work async, arguing that agent commits deserve better than Co-Authored-By, or just admitting that I’m getting tired of the AI discourse. The work itself is still interesting, even if the hype is exhausting.

How I Got Here

I started writing code professionally around 2007 - PHP, .NET, some Go, and (yes) some VB6 - before settling into Rails. The dev-env tooling obsession interest kicked off as a side project around 2013 and has come back in waves ever since: vagrant-lxc, ventriloquist, and devstep were all different shots at the same target - git clone && cd into a project and start working without thinking about infrastructure. Those are archived now and my current take is crib, a small runner on top of the devcontainer spec: same problem, three iterations later, this time built on a spec someone else maintains.

The other thing I keep getting pulled back to is using tech for civic stuff. In 2017 I used serverless to help Operação Serenata de Amor flag suspicious congressional reimbursements and during the pandemic I built covid19br.pub to monitor official COVID-19 publications in Brazil. Haven’t touched that space since, but with how much easier it’s gotten to hack on things with LLMs in the loop, I probably should.

I started this blog in 2013, then life happened and I took an 8-year break before coming back in 2025. In 2022 I rebuilt the site on Hugo and some old content didn’t survive the transition - so if you find a broken link pointing here from somewhere on the internet, that’s probably why.

🤖 AI Use

I use AI as a coding and writing assistant, and I want to be transparent about how.

For code, it’s a pair programmer - sometimes driving while I review, sometimes the other way around. I wrote about that evolution in Skip the ‘No AI Days’ and an earlier post on resistance. Architectural decisions and quality standards are mine.

For writing, AI is a copywriter and editor, not a ghostwriter. Usually I brain-dump and it helps me structure, then I refine. Ideas and opinions are always mine.

Get in Touch

Questions, collaboration, or just want to nerd out about tech in general - reach out.

Thanks for reading! 🚀