Who’s holding the rope?

We are living through one of the most exciting periods in the history of software development. Thanks to LLMs, tasks that used to take hours - such as setting up a new microservice, writing test suites, or summarizing a long meeting - now take minutes.

Don’t get me wrong, I fully support AI as a tool. It’s like having a pair programmer, research assistant and devil’s advocate all in one. However, we must be mindful of a dangerous shift, the transition from using AI to accelerate our work, to using it to replace our judgment.

Five years have passed

In the tech world, that’s a long time. When I last posted, the world looked different. There was no Agentic AI, my daily stack was different, and, most importantly, my priorities were completely different.

After a long period of digital silence, I finally spent some time maintaining this site. I migrated everything to Hugo, replacing whatever clunky setup I had before.

However, this is not just about a blog migration; it’s about what comes next.

Have you ever wonder, what some people do in your company? What their mysterious corpo titles mean? Who do they manage? What are their day to day responsibilities? Is there any outcome of their work?

It looks like we’re talking about phantoms.

I’ve spent my whole career working for the IT companies, which were just before or in the middle of the digital transformation. During this amazing, 10 year long journey, I saw many changes, that were dictated by the corporation. One its tricks was creating a role for someone, just to make this person happy. No more reasons, no more other benefits for the company.

The problem

There’s a never-ending story. It’s still not ready for shipping after working for over 3 sprints on it. Your project manager asks you all the time whether the job is going to be finished within this millennium. Your product owner asks you at every single meeting: why did the new feature not go live yet. Sounds familiar?

This unhealthy situation decreases team morale. We will rush with design decisions, work longer hours, we may have a feeling of not getting a closure ever, and failing our team. In the end all these elements have negative impact on us. And we end up with random, uncaught bugs.

The idea of microservices is a really old one and the “microservices” buzzword got new life about 2 or 3 years ago. Despite this, it’s still something rather new for many people, who go crazy about using it at work. Because of these facts you should think about building a proper microservices awareness in your company. As you don’t want to build yet another distributed system when you don’t need it.

During the last few months I’ve been doing a lot of code reviews of simple code assignments that candidates get as a first recruitment task. This assignment requires basic programming skills like JAVA Collections API, design and some knowledge about best practices. The main purpose is to filter out developers who don’t fit the company. Getting through such code doesn’t seem entertaining. However, I came up with an idea to list 10 common mistakes. Make sure you avoid them next time when applying for a job position!