You have to be bad at something again

I grew up in Santa Catarina, in the south of Brazil. I studied there, did my research there, and got good at my job there. Then I moved to Geneva, and later to Barcelona, and had to be bad at a lot of things again. That turned out to be the point.

This is not a post about relocating. Most people reading it will not move country, and should not have to. It is about a mechanism that moving country makes impossible to ignore, and which you can trigger deliberately without a plane ticket.

The competence trap

Here is the shape of it. You join an environment. You are bad at it. You learn fast, because everything is new and the feedback is constant. After a few years you are good — you know the systems, the people, the unwritten rules, which meetings matter. Your effectiveness is high.

And your learning rate has quietly collapsed, because the environment has stopped asking you new questions. You are still working hard. You are just working hard on variations of problems you already solved.

The trap is that this feels excellent from the inside. Competence is pleasant. Being the person who knows how the thing works is pleasant. Nothing signals that you have stopped growing, because all the local indicators — output, reputation, how often people ask for your help — are pointing up.

Comfort is not the absence of effort. It is the absence of surprise.

What changing environment actually resets

What a genuinely new environment does is expose your defaults as defaults rather than as facts.

Engineering culture is a good example, because we like to believe it is universal and it is not. How much context is written down versus assumed. Whether disagreement is expressed directly in the room or handled quietly afterwards. What "done" means — merged, deployed, adopted, or forgotten. How much of a decision is expected to be documented before you are allowed to act on it. Whether being late is a scheduling detail or a statement about how much you respect the other person.

None of these are written in any onboarding document. You learn them by getting them wrong, which is uncomfortable in a specific way: you are not failing at the technical work, you are failing at the part everyone else finds obvious.

I would also warn against thinking of "Europe" as one culture. Geneva and Barcelona are both European cities and they run on different assumptions about time, directness and how work fits into a life. Moving between them was its own adjustment, smaller than the first one but not trivial. The generalisation you build in one place is a hypothesis in the next.

Language as forced humility

The most useful discomfort I found was linguistic. My Portuguese is native. My English is proficient. My French and Spanish are, honestly, basic.

What that does to you professionally is interesting. In your own language you are articulate: you can be precise, funny, persuasive, you can soften a hard message. In a language you half speak, you are approximate. You say the second-best version of your thought because the best one is out of reach. You are, briefly, the slowest person in the room.

That is information, and most senior people never get it. It tells you what your colleagues who are not operating in their first language experience every day. It makes you write more clearly, because you can no longer rely on charm to carry an unclear argument. And it removes the option of hiding behind fluency — the idea has to stand up on its own.

What transfers and what does not

Technical skill transfers immediately and completely. Python is Python. A distributed system behaves the same way in Zurich as it does in Joinville. Nobody has to re-learn how a database index works because they crossed a border.

Social capital does not transfer at all. The credibility you spent years building — people knowing that when you say something is risky it is risky — stays behind. You arrive with your skills intact and your reputation at zero, and you rebuild it in a context where you are also less articulate than usual.

That combination is genuinely humbling and it is the most useful part. It forces you to establish credibility on current evidence rather than on history. It also gives you a very direct education in what it feels like to be the newcomer, which changes how you treat the next one who arrives.

How to do this without moving country

Relocation is one way to force the reset. It is expensive and disruptive and it is not the only way. What matters is deliberately putting yourself somewhere your existing competence does not cover:

• Change the domain, not the stack. Going from e-commerce to logistics to travel teaches you far more than a new framework in a domain you already understand. The hard part of software is almost never the software.
• Take the role you are not obviously qualified for. The one where you will be the least experienced person in the discussion for the first six months.
• Learn something publicly, badly. A language, an instrument, a discipline outside engineering. Something where you cannot use your professional identity as a shield.
• Work with people who do not share your assumptions. Not people who disagree with your conclusions — people who did not start from the same premises.

The uncomfortable part

I want to be careful not to make this sound clean. Being a beginner again in your thirties, in a language you do not fully control, while still being expected to deliver senior work, is not a pleasant montage. It is months of operating below the standard you hold yourself to, and it does not feel like growth while it is happening. It feels like being worse at your job.

That feeling is not a warning sign. It is the price, and it is charged up front, which is why most people decline to pay it. The alternative is a career that gets more comfortable and less interesting every year, which is a slower and much more expensive way to lose.