Six Months in Manchester Changed Everything. Here's What Happened After
The moment I stopped waiting to "be ready" and just went
What six months of immersion actually does to you
It rewires you.
When you can't fall back on your native language, something clicks. You stop translating in your head and start thinking in the language. You order coffee, argue about football, debug code in standups, and explain your architectural decisions — all in English, all in real time. There's no pause button.
By month three, I was holding technical conversations I never thought I could. By month six, I was thinking in English before I realized I was doing it.
Immersion works because it removes the safety net. And removing the safety net is exactly what accelerates learning.
The insight that changed how I study
When I came back, I expected to just... coast. Six months felt like enough.
It wasn't a failure — it was the best education I've ever had. But fluency isn't a destination you arrive at. It's something you maintain, like fitness. You don't go to the gym for six months and then stop forever.
The real insight was this:
Fluency is built through accumulated hours of exposure. Not through a single trip. Not through a course. Through hours.
Listening hours. Speaking hours. Reading hours. Writing hours. They compound, quietly, over time.
How to build those hours without moving to England
You don't need a visa. You need a system.
Listen relentlessly. Technical podcasts, conference talks, YouTube without subtitles. The ear is the most underrated muscle in language learning. If you're not constantly exposed to how real English sounds — its rhythm, its filler words, its accents — you'll always feel one step behind.
Speak before you feel ready. Switch your meetings to English even when you could use Spanish. Leave voice notes in English. Comment on GitHub in English. The discomfort you feel is the feeling of growing. Lean into it.
Read from the source. Official docs, books by engineers you admire, blog posts from the people building the tools you use. In English, as written, without translating. Slower at first. Then faster than you'd expect.
Write in public. Forcing yourself to articulate technical ideas in another language makes you a sharper thinker and a better communicator. Start with small things — a tweet, a comment, a short post.
Why this matters more than most things in your career
English in tech isn't a nice-to-have. It's the language where everything happens — architecture debates, incident postmortems, the conversations between the engineers who are building the future.
If you can't access that conversation directly, you're always reading a secondhand summary.
Manchester gave me the confidence to jump in. But the hours I've put in since then — every podcast on a commute, every README written in English, every uncomfortable meeting where I chose to speak up — that's what built the fluency.
You don't need six months abroad to start. You just need to start.
The hours will do the rest.
How many hours of English have you gotten this week?
