retrospective

From the beginning, the focus of this blog has been technical, very rarely organizational. I broke this unwritten rule once in 2015. I began writing retrospectives in 2023 on the year that had passed. Let’s continue the tradition, but with a wider scope than before. The situation warrants it. More chaos It’s a hard realization to admit, but the world is spiraling deeper and deeper into chaos. Russia’s invasion of Ukraine has now dragged into its third year, and still, neithe

For the first post of 2025, I’m continuing my retrospective series. As last year, before diving in into the report proper, I’d like to remind you that Ukraine is still fighting for its survival after nearly 3 years and countless Russian war crimes. The civilized world can’t allow rewarding the invasion of a sovereign country, lest we see more invasions. Remember that in 1938, in Munich, European 'leaders' acknowledged Hitler’s annexation of Czechoslovakia’s Sudeten

An exciting part of software development is what was unanimously considered good practice at one point in time can be more ambiguous years later. Or even plain wrong. However, you generally need to do it multiple times over time to realize it. Here are my top learnings from my experience in Java projects. Packaging by layers When I started my developer career in Java, every project organized their classes by layers - controllers, services and DAOs (repositories). A typical project’s str