Weekly review cw 09

Politics

On election Sunday, I watched the reporting until late in the evening. At that point, it was still unclear whether a coalition with two partners would be sufficient. Fortunately, neither the FDP nor the BWS overcame the five percent hurdle. This means that the black-red coalition has the opportunity to turn things around—even if I don't believe it.

Regardless of that, I'm just shocked. The CDU's plan to remove votes from the AfD with its right-winged agenda has not worked. That was expected, but it illustrates the danger and idiocy of countering the shift to the right by steering to the right. The rest of the week did not go well - the list of questions and the position on the debt brake show the CDU's long-term orientation and tactics.

On one point, I agree with Mr. Spahn's statement that the next four years will decide what kind of catastrophe could result in the 2029 elections. However, the leadership team around Merz is misinterpreting their role. They are not supposed to please the AfD voters, but rather to separate migration policy and the shortage of skilled workers from security policy and the fight against crime.

Sport

System training was on the agenda for Monday and Tuesday evenings to counteract Sunday's frustration. It was two intensive hours each under the direction of third Bundesliga player Philipp Floritz. I am convinced that this is how my club, the NTSV, and its players will progress.

The week naturally continued with the push-up challenge—100 daily push-ups have become easy. The only annoying thing is my right wrist, which is starting to hurt. To counteract this, I bought holders, so I don't put my wrist directly on the floor but in a straight extension of my arm. I can only recommend this: Amazon affiliate link.

The week is rounded off with a lot of table tennis. We have the team from the bottom of the table as our guest on Friday evening. On Saturday, I accompanied our 1st boys' team to the last match day in our home hall. Sunday is our third NTSV Ditsch tournament, which external players also signed up for and want to participate in. Word is slowly getting around how much fun this format is!

Obvious versioning of back-office applications

When developing software, we at konzentrik use the Semantic Versioning concept. The upcoming release is automatically given a version number based on the change history. This is usually determined and saved when the production code is built.

In contrast to the code that runs on the server side, this version number must be displayed for back-office applications so that the customer can pass on this information when describing errors. This makes it easier for me to find the mistakes—I can look at precisely the version the customer is running and understand the error more quickly. If I have to guess at this point because I'm not sure whether the latest version is installed, it complicates my work.

I could not meet the above requirements 100% with my previous approaches. This week, however, I found a way. I will summarize the technical details in an article soon, hopefully making life easier for other developers.

Documentation challenge

About a month ago, we secured the development server for a project by blocking all ports, thus preventing easy access to services such as the database. However, to still grant ourselves access, we devised a clever solution, implemented it, and were happy it worked.

I wanted to access the database this week, but I couldn't remember how. Because the solution was so simple (and clever), I didn't document it. At the time, I didn't think about my future and was sitting in front of the computer, extremely frustrated and desperate.

I wrote a note in my bullet journal for the improvement potential meeting on Monday: Write a joint developer diary. Whether this is the way to go or a different approach - I want to avoid being faced with the same situation again. I will report on which path we take and whether our solution works.