Hello World: All I Want You to Know About Me!

Hello!

Glad you stopped by my blog. This is a place where I’ll write about things in the world of technology that interest me — from technical topics and engineering experiences to AI, architecture, security, and trends that still aren’t clear what problem they’re actually supposed to solve.

Not everything I write here will necessarily be part of my current work stack. Some of the topics that interest me sit right at the intersection of several domains. One day I might write about React or NestJS, and another day about caching, reactive programming, security, or a new trend.

When I bring up a topic, I hope to have something to add to the conversation — an experience, an analysis, a question, or at least a point of view. If you’re here looking for my work stack or professional experience, I’d be happy to talk directly.

Career Path and How I See Programming

Choosing programming wasn’t particularly romantic for me. When I was deciding on a career path, what mattered was how much creativity the job required, how involved it was with current technologies, how much social interaction it demanded, and of course the income. Programming checked those boxes, so I continued my studies in that direction.

My professional path wasn’t linear. Over the years I tried Frontend, Backend, Java, Android, Data Analysis, and several other areas. What became more important than the technologies themselves was learning how to make decisions about direction: when to keep going deeper, when to change strategy, and how to use what each experience taught me to make better decisions next time.

Today I don’t see programming as just writing code. System design, problem-solving, analyzing trade-offs, understanding why a decision was made, and working with people to reach a concrete outcome are all parts that interest me. I’m not even sure that a few years from now I’ll still see myself purely as a developer. My interest in decision-making, systems, and management keeps growing, and my career path may move more in that direction. I don’t have a definitive answer yet, and I’m fine with that.

A Few Work Traits That Matter to Me

Order and predictability in work are important to me. I like knowing what’s happened and keeping things under control as much as possible. That’s why I’ve been writing daily reports for a long time, defining clear work blocks for myself, and periodically reviewing my performance.

Curiosity is another big part of how I work. If something genuinely interests me, it’s hard to just walk past it. I usually prefer understanding something over merely memorizing it — once I grasp the structure and the connections between concepts, learning the rest becomes much easier.

Results-orientation is another trait that has both helped and sometimes hindered me. It matters to me that the work I do eventually leads to a tangible outcome. At the same time, I’ve learned that not everything is supposed to produce results immediately.

In technical discussions, logic and reasoning matter to me. When I disagree with someone, I’d rather the goal be figuring out which of us is wrong than simply winning the argument.

What This Blog Is Going to Look Like

I’ll try to keep the posts categorized and as technical as possible.

Some of the writing will be directly about software engineering — Frontend and Backend, architecture, performance, caching, state management, technical debt, distributed systems, and similar topics.

Another part will be about AI and its impact on software development. I’ll probably talk a lot about new hypes too — both the ones I think are genuinely important and the ones I believe are being taken more seriously than they deserve.

Security, reliability, scalability, and some topics at the boundary of technology and society will also have a place here. In some posts I may simply want to discuss an idea or claim: whether a new tool actually solves a problem or is just a new abstraction on an old one; or whether a new trend is really worth following.

My goal isn’t to claim I have the final answer on any of these topics. One of the things that interests me is the process itself: finding a question, investigating it, examining our assumptions, and seeing what answer we ultimately reach. And if it later turns out we were wrong, that’s part of learning too.

Now That You’re Here...

This blog is ultimately a place to record the things I learn, experience, and think about in a more organized way. I hope none of the posts are written just so there can be “a new article on the site.”

If you read something here, I hope it has at least one point. If you disagree, even better — I’d be happy to talk about it. And if you think I’m wrong, tell me why.