This morning I created a Slack channel called #counterpart-português. By the end of the day it had a channel description, a welcome message, a company-wide announcement, and a real conversation happening in Portuguese — engineers thanking each other, asking questions, expressing things they’d probably been holding back.
I don’t speak a word of Portuguese.
All of it was written with Claude. I wrote in English, Claude translated, I posted. When engineers replied in Portuguese, Claude translated back. The round-trip took seconds. Nobody could tell the difference — and honestly, that’s the point.
The Idea Came From a Belief, Not a Feature Request
This didn’t start with a productivity initiative or a diversity checkbox. It started with a conversation with Eli Evans, an engineer on my team who believes — deeply and vocally — that people need a safe space to do engineering.
Not just to work. To think. To question. To make mistakes and grow without unnecessary friction standing between the idea in their head and the words coming out.
That stayed with me. When I sat with the Broker Services team and turned it over, the conclusion was obvious: for engineers who think in Portuguese, working constantly in a second language isn’t merely inconvenient. It’s a real tax on quality, creativity, and confidence. Every time you translate a thought before expressing it, you lose something — the precision, the nuance, the speed. The gap between what you understand and what you can communicate in real time is where good ideas go quiet.
So we asked: what if we just removed that barrier?
What Actually Happened
Here’s what made today a breakthrough rather than just a nice gesture: this wasn’t possible through goodwill alone. Someone would have needed to speak Portuguese. Or we would have needed a dedicated translation workflow. Or the channel would have become an island — warm in intention, impractical in execution.
What made it work is that Claude has access to our entire system via MCP — Model Context Protocol servers connecting it directly to Slack, Linear, GitHub, Sentry, Snowflake, and Salesforce. That means Claude isn’t just a translation layer sitting outside our work. It’s woven into the infrastructure where the work actually happens.
A Portuguese-speaking engineer can now have a conversation in Slack in Portuguese, file a Linear ticket in Portuguese, get a Sentry error summary in Portuguese, and review pull request context in Portuguese — all in real time, all connected to the same live systems everyone else uses. The language barrier isn’t routed around. It’s dissolved at the infrastructure level.
I wrote about this on LinkedIn today in Portuguese. I don’t speak Portuguese. That sentence shouldn’t be remarkable. But it is, and that’s the thing worth sitting with.
I’ve been thinking a lot lately about what it means for AI to be genuinely useful in an organization rather than just impressive in a demo. The pattern I keep coming back to is this: the highest-value applications aren’t the ones where AI does something new. They’re the ones where AI removes a cost so quietly and completely that it stops feeling like a workaround and starts feeling like the way things just work.
Language has always been an invisible tax on collaborative engineering teams. We accepted it because we had no choice. The dominant language of the team became the dominant language of thought, and everyone else paid the translation toll — in cognitive overhead, in confidence, in the subtle self-editing that happens when you’re not quite sure how to say what you mean.
Today that tax became optional.
That’s not a small thing. That’s the kind of shift that, five years from now, we’ll look back on the way we look back on remote work infrastructure — as the moment something that used to require sacrifice stopped requiring it.
Credit Where It’s Due
None of this would have happened without Eli’s belief that safe spaces matter in engineering — not as a cultural nicety, but as a prerequisite for quality work. And without a team that embraced the idea immediately, the channel would be an empty room.
The technology made it possible. The people made it real.
That’s always the order that matters.
Leave a Reply