Hi, I’m Catalin.

I enjoy following a problem from the first conversation through to something people can use. That means listening, questioning the assumptions, working through the design, writing the code, and finding out what I missed once it’s in someone else’s hands.

I keep coming back to three questions: What happened? Why did it happen? What can I do next? Whether I’m working on an interface, a developer workflow, or a way for people and AI to share context, I want the answers to feel within reach.

And I care about the details. A clear explanation, a well-placed interaction, a little colour. Making something useful and making it enjoyable are both part of the work.

At Miro, I helped deliver our internal Iteration Platform as part of a two-person team, and I continue improving it. It helps colleagues work with feature flags, rollouts, and experiments. My focus is product, frontend, and client SDKs; my teammate handles backend and infrastructure.

I’m also exploring practical ways for people and AI to work together. One of those is a research hub that keeps track of context, decisions, and unfinished work, so I can return to a topic without reconstructing everything from memory. A few helpful robots are involved. 🤖

• Building internal platforms around developers’ needs ↗Published at Miro · The platform and the people using it
• A research hub that remembers my work ↗Published at Miro · Context, decisions, and a few lessons along the way

I started in .NET, then moved into frontend development and spent several years with Angular, much of that at SnappCar. These days, my work spans TypeScript and JavaScript, SDKs, UI/UX design, and AI workflows.

I’ve changed my mind along the way, too. I’ve written about walking away from a NativeScript decision, alongside smaller discoveries in CSS, animation, and everyday frontend work. This blog is where I share what I’m learning, including the parts that didn’t go according to plan.