posts

A Software Engineer is a professional responsible for designing, building, testing, and maintaining software systems. This title signifies not only technical expertise but also the ability to think critically, solve complex problems, and collaborate across various domains.

In the world of small tech companies, where every minute counts in the race for market relevance, it’s easy to lose sight of the fundamentals. Many of these companies possess great potential but fail to capitalize on it. Here are stories that could happen anywhere, highlighting the recurring pitfalls in small organizations.

Poland stands at a pivotal moment in its economic and political development. The strategic decisions made today will shape the country’s future for decades. Prioritizing STEM (science, technology, engineering, and mathematics), investing in cutting-edge technologies, building industrial capacity—including defense—and simplifying legal frameworks are essential steps to make Poland more independent, prosperous, and secure. Below, I outline the key reasons why this direction is critical.

Modernizing software architecture in a financial institution often feels like an uphill battle. Strict security policies, siloed teams, and legacy processes create obstacles that hinder agility, innovation, and collaboration. As the sole developer in such an environment, you may feel overwhelmed trying to align the technical needs of the system with the rigid structures of the organization.

In today’s fast-paced software development landscape, organizations are constantly seeking ways to streamline processes, improve code quality, and deliver value faster. One often overlooked yet crucial aspect of achieving these goals is the feedback loop during development and testing.

Traditionally, many teams have operated with outdated practices that hinder their ability to respond quickly to issues. Let’s explore how embracing tools like TestContainers can revolutionize testing workflows, save time and resources, and have a strategic impact on your organization.

This October, I embarked on a one-year postgraduate course in Cybersecurity Engineering at the Warsaw University of Technology. Interestingly, this was not my original plan. Two years ago, inspired by the growing prominence of Artificial Intelligence, I considered pursuing a related program. AI was (and still is) an exciting field, with significant breakthroughs capturing headlines worldwide.

As a software engineer working with JVM technologies, my daily work revolves around high-performance computing, efficient workflows, and seamless tool integration. Over the years, I’ve realized that the choice of my laptop is crucial to my productivity and overall work experience. While some companies may choose to provide engineers with Windows-based machines, I firmly believe that MacBooks—especially in the context of software development—offer far greater benefits in terms of performance, security, and overall usability.

This article will explore why MacBooks have become my preferred choice for professional work, from pragmatic technical reasons to the more subtle aspects of familiarity and comfort.

When I was part of one of the largest eCommerce companies in Europe, I observed something that still makes me reflect today. As an employee, I often felt like the distinction between the leader and the team wasn’t as clear as it should have been.

Leaders are often seen as the ones with the final word, the decision-makers, and those who keep the team on track. However, there were moments when I felt that leaders didn’t always know how to navigate situations where the team disagreed with company decisions. It made me question: Is a leader truly just a representative of the company, or are they supposed to be a part of the team too?

Schizophrenia is a deeply challenging and often misunderstood illness. My brother, once a thriving athlete with incredible determination and the ability to achieve any goal he set, was diagnosed with schizophrenia a few years ago. It has been a heartbreaking journey to watch how this illness has impacted his life, his dreams, and the rhythm of our family.

The medications he has been taking for years, while essential to managing the condition, have caused significant weight gain—30 to 40 kilograms. These same medications require constant vigilance: regular blood tests, frequent doctor visits, and ensuring that he takes them as prescribed. The side effects extend beyond physical changes. They often leave him sleeping half the day and struggling with energy to engage with the world.

Four years ago, I took my first step into volunteering at a soup kitchen run by the Capuchins. While everyone refers to it as “going to Miodowa,” the actual soup kitchen is located at Kapucyńska 4, just around the corner from the church on Miodowa Street.

At the time, I was nervous. I imagined it would be a one-time experience, something that might feel awkward or uninspiring. I thought I’d be surrounded by clergy and feel out of place. But the reality turned out to be far different, and far more enriching, than I ever could have imagined.

Domain-Driven Design (DDD) has become a powerful tool for modeling complex systems in a way that aligns with the business. One of the key concepts in DDD is the subdomain—a partitioning of the business logic that helps teams build maintainable and scalable systems. While many developers and architects understand the basics of domains and subdomains, there’s a lot of potential hidden behind these terms.

In this article, I’ll explore subdomains in detail and introduce a set of heuristics that can guide the discovery of subdomains. Along the way, we’ll discuss how these heuristics can be used in real-world scenarios, and I’ll suggest visual tools that can aid in their application.

Hi, I’m Kamil, and welcome to my blog. Here, I’ll be sharing insights on software architecture, offering practical tips and strategies based on my experience as a software engineer. Stay tuned for valuable content that will help you navigate the complexities of software development more effectively.