Portfolio

In the first post, I wrote a bit about myself, in case any employer or recruiter happens to visit here. I should add that the page you're currently viewing will continue to be developed, modified, and improved. This is what I managed to put together over the weekend with the help of my friend Claude. It's good enough for a start, though please don't treat it as a portfolio (yet).

I was taught that to begin, you shouldn't strive for perfection—it's enough to have something that's good enough. And since I can write to you, that's exactly what this is.

What will it be about?

About programming, about life, and about the life of a programmer. When I was a young developer, in my industry, everyone who started a blog said they were doing it to learn something themselves. Nobody dared to be experienced enough to tell others how they should program. I dare a little, but I also want to learn something.

However, this won't be a purely technical blog. It will be about how an analytical mind finds its way in a world where soft skills have gained significance. I suspect the posts will be irregular and short, as time permits between work, personal projects, and family.

I am an experienced developer who has broken many things and fixed just as many. I enjoy creating new things, and I'm not afraid of legacy and messy projects. I enjoy learning new things. Within a reasonable time, I can adapt to any technology stack, which I have done a couple of times already. Picking up any programming language is also not a problem.

While I always welcome new technologies with an open mind, years of work have made me prefer proven paradigms and methodologies that result in stable production code and no sleepless nights. I can adapt to the team's style, but personally, I appreciate clean object-oriented programming without shortcuts, strongly typed languages, which, contrary to appearances, stems from my work in Python - design patterns, domain-driven design, and unit testing. I'm also a strong advocate for small, cross-functional teams, especially those that include QA. My code will be boring but stable, and my work will be documented.

I also have experience with and understand agile methodologies, including Scrum, Kanban, and SAFe. I work well with people, and I prefer working remotely. I have a well-equipped home office, tailored to my needs, and I'm productive working from home. I take work seriously. For me, it's primarily about a secure home, family well-being, and my children's future. I don't slack off. I have strong internal motivation coming from discipline. I do what needs to be done. I don't need to be enticed with benefits, shiny novelties, motivational slogans, or fruit Thursdays.

I can commit, and I want to commit to long-term cooperation. I diligently fulfill my responsibilities and make every effort to ensure both the product and code are of the highest quality, the client is satisfied, and my colleagues aren't burnt out.

I use the widely available and popular AI tools. Primarily for learning, but also for programming. I work with them wisely, not leaving them too much autonomy, and I've developed my own methodologies that have yielded very good results so far. I don't like taking shortcuts or rushing development.

I have strong mathematical and algorithmic foundations. For questions about specific algorithmic problems, I would need to refresh my memory, but my greatest strength is the ability to think and solve problems - not only technical ones, but also product-related. I'm not someone who just waits for someone to tell them what to do. I actively think and suggest what might be worth considering, and when the feature development slows down, I try to improve what already exists.