Building from Frankfurt

I didn't plan to end up in Frankfurt.

I grew up in Rajshahi — a city in northwest Bangladesh known for mangoes, the Padma river, and a stubborn kind of quiet. I wrote my first lines of PHP there, staying up past midnight because that was when the ideas wouldn't stop.

Then I moved to Dhaka for my B.Sc. in Computer Science at Southeast University. Dhaka taught me a different kind of hustle — 20 million people, permanent traffic, and a tech scene building itself in real time. I built things, shipped things, learned what it actually meant to write software for clients who depended on it.

Then came Germany. Three universities, three cities (Zwickau, Würzburg, Heilbronn), a Masters that spanned Management & IT, AI & XR, and Software Engineering. And somewhere in the middle of all of that: Frankfurt.

Frankfurt was the anywhere that happened.

The adjustment nobody warns you about

People talk about the practical stuff when you move countries. Visa, bank account, Anmeldung, finding a flat with a landlord who doesn't immediately close the browser tab when they see a non-German name. That part is hard. What nobody talks about is the quieter thing: the feeling of starting from zero socially while your professional life continues at full speed.

I was shipping code, talking to clients, debugging GDS integrations — all in English, all remote — while simultaneously having no idea how to buy a monthly transit pass without accidentally signing up for something I didn't want. The Deutsche Bahn app still defeats me sometimes and I've been here years.

But Frankfurt is a city that doesn't demand you perform belonging. It's international, transactional, efficient. The cafés in Sachsenhausen don't care where you're from as long as you order the Apfelwein or the espresso and leave them alone to do their thing. I found that refreshing.

What working alone in a new city does to your code

I think the isolation of those early months made me a better engineer. Not through some romantic struggle narrative, but simply because I had a lot of quiet time and no excuse not to use it.

I read more. I got obsessive about API design in a way I hadn't been before. I started finishing side projects instead of abandoning them. I built my first proper travel tech integration — not for a client but because I wanted to understand how the whole flight booking chain actually worked from search to PNR issuance.

That project became the foundation for Trip Begin — an OTA I founded that does exactly that, for real travellers, with real bookings. Alongside it came Tourist eSIM (a global eSIM marketplace for travellers) and Cloudlax IT (a hosting platform I co-founded). Three companies. All shipping. All started in this city.

The espresso theory of productivity

There's a café near my flat where I've probably written more production code than anywhere else. The owner knows my order. The wifi is unreliable enough that I can't fall into meetings accidentally. There's a window that faces the street.

I've come to believe that your environment shapes what you build. Not the tooling, not the framework — the actual physical context. The café forces a certain kind of focused, unhurried thinking that my desk at home doesn't. The train to Berlin forces reading. The walk along the Main River forces nothing at all, which is exactly when the architectural decisions tend to untangle themselves.

Frankfurt is weird and I love it

Frankfurt has a skyline that looks like Manhattan got dropped into a German village. It has the highest density of banks in Europe and also one of the best Christmas markets. It's a layover city for a lot of people — I know because I was one of them before I stayed.

Now I see it as a genuinely strange and underrated place to build things from. International airport, central European location, quiet enough to think, connected enough to get anywhere. If you're going to work in travel tech, there's something poetic about living in one of the world's great transit hubs.

I'm still here. Still building. Still figuring out when exactly to use the formal Sie versus the casual du. But the code is shipping, the espresso is good, and the 5am trains are always on time.

That's enough for now.