If you’ve landed here, we probably work together or might end up working together! Use this README as a way to get to know me better: my personality, the way I work, and what makes me tick.

I have a great sense of humor, and by default, I never take anything personally. Jokes (especially dad jokes) and memes are always welcome. Having lived in the UK for many years, I’ve developed a tendency for self-deprecating humor and casual chitchat about the weather.

I’m a positive person and tend to cheer people up when times are tough. But even superheroes need a break! If I’m not in my usual good mood, give me a bit of time to recharge.

I’m flexible and usually favor the least painful solution. However, if the proposed approach involves technical debt, data migrations we could avoid, or doing things twice, I’ll invest the necessary time and energy to demonstrate why the “right way” is better. And this might mean pushing back deadlines or revisiting tasks, but it’s always in the spirit of building better solutions.

I’m always striving to grow and improve, and feedback is crucial for that. If you notice something I could do differently, do better, or perhaps stop doing altogether, feel free to have an open discussion with me or drop me a DM.

I’m definitely more of an extrovert than an introvert. When I go to the office, I enjoy having lunch together, grabbing a coffee, and connecting with people. I love getting to know more about my colleagues, not just their work or favorite programming language!

I like improving things, and for that, I need to understand what I’m doing. I prefer spending a bit of time upfront to dig into an issue—especially if it’s outside my team or domain. When asking for someone’s help or opinion, I typically provide context in a message beforehand so they can prepare before we jump on a call. I appreciate the same consideration when someone asks for my hand.

Over the years, I’ve become accustomed to working remotely, including asynchronously, so clear and concise text messages are crucial for me. If there’s no time for that, a quick call is better than poorly written messages. Additionally, sending non-urgent messages outside of work hours, especially when tools like Slack and Gmail have scheduling options, can be a bit disappointing. 😉

In meetings, I’m not always the most vocal person. Please don’t mistake my quietness for disengagement. Depending on the day and how inspired I feel, I might contribute more or less. Sometimes, I lead discussions; other times, I take a backseat to listen. I also like adding thoughts asynchronously when the time feels right.

For complex solutions, potentially “dirty” (code- or architecture-wise) ideas, or anything with long-lasting impact, I’m always up for brainstorming. Whether it’s a whiteboard, Excalidraw, FigJam, or another tool, let’s figure out the details, trade-offs, and the best path forward together.

As I said above I am pragmatic, and I approach pull request reviews the same way. I’ll clearly distinguish between blockers and opportunities for improvement. And please never take my comments to improve as a personal attack, we’re all in the same boat! If discussions get too lengthy, I strongly advocate for a call to pair review and resolve issues more efficiently.

I enjoy pair programming and have been doing it more frequently in recent years. If you need a second pair of eyes or even a rubber duck to talk through your ideas, don’t hesitate to reach out.

’m a DIY enthusiast. I refurbished a trader’s van into a cozy campervan (happy to share pictures if needed!) and have also built furniture, including a patio pergola. I enjoy running, surfing, and trying out different types of sports.