About BalassLabs
I'm Robert Balassan, a developer from Bucharest, Romania. BalassLabs has existed in a few different forms, mostly as a personal space where I learned, built, changed direction, and figured out what kind of work I actually wanted to put into the world.
How BalassLabs evolved
This project did not start as a finished brand with a fixed plan. Over the last five years it went through different versions, and the site, API, and general architecture kept getting improved as I learned more.
I did not keep throwing everything away and restarting from scratch. Aside from branding changes, most of the work was iterative. Keep what still made sense, replace what no longer did, and make the stack stronger over time.
Even though the project had lived under a different domain for a while, BalassLabs stayed a personal exploration for most of that time. I had not pushed it all the way to a proper public release until now.
How I got into development
I started learning programming back in 2018. I do not come from a software background. I studied electrical engineering, but after a while I realized I wanted a different direction.
What pulled me in was the fact that development lets me create things directly. It gave me a path that felt both creatively satisfying and professionally meaningful, something I could grow into for the long term and also rely on financially.
That shift mattered to me because it was not only about changing tools. It was about moving toward work that actually felt like my own.
Games, game engines, and creative exploration
I've been a PC gamer for as long as I can remember, so games were always going to stay close to what I do. During these years I built templates, prototypes, gameplay mechanics, and technical experiments while moving back and forth between Unity, Unreal, and Godot.
If you spend enough time around game development, every engine eventually gets presented as the best option for someone. Instead of picking a side too early, I used that time to explore the free-to-use engine landscape for myself and understand what each tool is actually good at.
That back and forth helped me build a broader perspective, not only on engines, but on tradeoffs, workflow, and what different kinds of projects really need.