About
A builder, entrepreneur, engineer, and lifelong learner.
My path into software was not a straight line. Before engineering became my profession, I spent years around entrepreneurship, startups, finance, investing, and web design. Over time, those interests started to connect into one direction: building useful, well-crafted digital products.
Before engineering
Before I fully turned my life toward software engineering, I was involved in different projects, businesses, and startup ideas. A large part of my interest was connected to finance and investing, where I spent a lot of time thinking about markets, strategy, risk, discipline, and long-term value.
That background shaped how I think today. I learned to look at problems not only from the technical side, but also through purpose, timing, tradeoffs, and outcomes.
The thread that stayed with me
Through all of those years, web design was always there. It started as a personal passion — something I kept returning to because it combined creativity, structure, technology, and communication.
I liked the feeling of taking an idea and turning it into something visible, usable, and alive on the screen. After moving to the United States, that passion became more than a side interest. I turned it into a real profession.
What keeps me moving
Even outside of work, I usually have something in progress. I keep working on personal web projects, testing ideas, exploring new tools, and building small things because that curiosity never really turns off.
I also help my wife with her business and web application, which keeps me close to the practical side of software: real users, real needs, real constraints, and constant improvement.
How I see technology now
I read a lot, study continuously, and try to stay close to where technology is moving. What excites me most right now is how quickly the world is changing — how new tools, AI, automation, and software are reshaping almost every field.
That pace can feel overwhelming, but I find it energizing. To me, strong engineering today is not only about knowing one technology deeply. It is also about being flexible: learning quickly, moving between tools, understanding unfamiliar systems, and applying clear judgment to new problems.
That is the difference between simply writing code and becoming an engineer: not being attached to one stack, but being able to understand the problem, choose the right tools, and keep evolving with the work.