Move First, Code Later: How X-Team Developer Michal Nawrot Balances Focus With Creativity

Michal Nawrot does not solve problems sitting in front of a monitor. He goes for a walk. He has lunch. He works out. Then — usually — the answer arrives.

That approach might sound counterintuitive for a full-stack JavaScript developer, but Nawrot, who lives in Poland and works with X-Team, has built his entire working life around a simple principle: the best ideas come when you stop forcing them. He's tested this theory across triathlon training, motorbike trips through Europe, a philharmonic concert at the Sydney Opera House and a dinner of kangaroo on an Australian farm. The box, he has found, is a lot easier to think outside of once you've physically left it.

In this story, Nawrot shares how an indecisive teenager drawn to art and music ended up in software, why remote work changed the way he thinks about focus and creativity, and what it looks like to treat life's biggest ambitions as problems with practical solutions.

From Audio Engineer to Front-End Developer

Nawrot describes his teenage years as a study in indecision. He had an episode with electronic music and wanted to become an audio engineer, but couldn't figure out how to make it happen. So he turned to IT — demanding enough to keep him engaged — while freelancing as a graphic designer on the side for creative relief.

The two tracks eventually merged. He started coding animations and increasingly complex web interfaces, and front-end development followed naturally. The work appealed to the same part of him that had been drawn to audio engineering and design: it was technical and creative in equal measure, with a visible result at the end.

That dual pull never left him. Today, what keeps him moving forward in his career isn't any single technology — it's the challenge itself. "A challenge gets me excited," he says, "whether that's deciding on a non-trivial, technical matter, seeking the best or most suitable solution for something, or learning a new language to understand and solve something." Challenge alone, though, isn't enough. He needs to believe the work adds value somewhere — that it's part of a step forward, not just an exercise.

His early career offered one of those formative moments. At the end of his studies, as part of his master's thesis, he joined a group of scientists working on a risk and quality assessment methodology. His task: invent and implement a visualization module for the tool supporting their research. He built a single-page application at a time when Internet Explorer 6 was the newest IE release and the team used SOAP for client/server communication — REST APIs were nowhere in sight. After extensive optimization, it worked. Later, at his first job after university, he worked as a Flash developer on a project building chatterbot visualizations for automated customer support, using pre-recorded video sequences of actors combined with synthesized voice to simulate talking avatars. The company was small enough that he also had the chance to prove himself as a director, coordinating actors, stylists and camera operators when a bigger client needed dedicated video sequences.

Why Remote Work Is Better for the Work

Nawrot focuses easily anywhere — a crowded cafe, a train, a plane. The location has never been the issue. What matters is whether he's had space to think away from the screen first.

"Commuting to then spend 8 hours at the office has never been effective for me," he says, "because I'm not creative sitting in front of a monitor the whole day. Remote work allows me to balance my focus and creativity." The walk that clears his head, the workout that frees up a stuck problem — those only happen reliably when the workday isn't bracketed by a commute on either end.

Remote work also changes how he interacts with the industry. An office, he believes, creates a kind of boundary: developers inside them can develop internal fixations that are hard to overcome. Working remotely means interacting with people from other cultures, which widens perspective and makes him more open to new solutions. Different time zones require better planning and communication, which in turn makes Agile practices more effective rather than less.

And then there's travel itself. "The great advantage of working remotely is that I can do it while traveling," he says. "There are so many great things all over the world that can inspire me. To think outside the box, you need to escape it first."

Big Dreams, Practical Thinking

Nawrot is deliberate about not setting long-term goals in his technical work. Setting them too far out, he says, kills flexibility — and flexibility is essential to him as a software engineer. He might have a rough sense of what he'll focus on for the next two months, but anything beyond that can shift if something more valuable comes along.

His personal ambitions operate on a different logic. Finishing a full Ironman race, practicing Muay Thai in Thailand, riding his motorbike across Europe, tasting wine from the best vineyards — he's done all of it. The secret, he argues, isn't willpower but framing. "A marathon is just 4 hours of hard work," he says. "People work 8 hours a day and are perfectly fine. If you want to be an astronaut, simply save up for a trip on the Virgin Galactic!"

The point is that the distance between a dream and a plan is usually smaller than it looks. For Nawrot, that philosophy extends to everything: the career he built from conflicting teenage interests, the remote life he designed around movement and curiosity, the feats he keeps adding to a list that most people file under "impossible." Anything is possible, he says, if you focus on what's important.

Ready to build work you're proud of? Apply for an open role at X-Team.