Typescript is basically just Javascript with slightly stricter rules and powerful types. This simple addition is actually surprisingly beneficial and allows us to have powerful intelli-sense in our editors and IDE’s. Typescript also gives us quick feedback when we have made mistakes and cause type conflicts. It’s no surprise that many developers like to use it and enjoy its features. But how do we actually use types and what can we do better? Let me introduce branded types to further improve our developments and get the most of it.

Spring has been providing a reactive web client for some time. Although this client provides many settings, not everything is so obvious and simple. For example, during development I often want to see exactly how the server is responding or ignore certain errors. For this I would like to configure the client in such a way that I can notice such errors and react accordingly.

Almost every Java developer knows Project Lombok. It is one of the most widely used libraries and keeps popping up somewhere. The advantages are obvious and are shown very clearly on the project page. Even so, not everything Lombok does is good and there are some pitfalls using it. I want to dwell a little here on the issues I see in using Lombok. I am not concerned with avoidance, but rather with awareness of weaknesses and pitfalls.

As a developer, I always have to deal with various projects. Many of them differ significantly from each other, others are very similar or related to each other. However, what unites them is the fact that I had organized them poorly in the past. Later I started to think about the folder structure and to organize it better. In this article I would like to explain this organization to you and describe how I got there.