I'm a T1D and tbh it's not that hard to manage, I just wouldn't need that. But for kids or the elderly, I see a use case.
The hardest to learn was that an unhealthy lifestyle resulted in a diabetes that was harder to manage. Too much carbs, not enough exercise, etc. After adjusting my lifestyle, it became quite easy.
The most pain, in my experience, comes from the discrepancy between the CGM - measured value and the prick-test value, even when accounting for time lag. I've used several CGMs and they've all been wildly off sometimes. I have a few T1D acquaintances who relied on their CGM alone and have significantly improved their HbA1c after accounting for that.
I thought "Dominate or be dominated" was the problem you saw in democracy?
Well, then I guess Germany's example is not too bad.
"CDU/CSU + SPD coalition won a majority" ... well, no. That's not how it works at all.
CDU and SPD did not win a majority together, since they were opponents in the election, and fought tooth and nail over, for example, immigration issues. They did not, at all, campaign together.
They both failed to win over half of the parliament seats. In simplified terms, they both lost. Everyone lost, if you will, because the system is not designed for anyone to easily win over half of the parliament seats.
That's why they had compromise and form a coalition. Thus no-one rules completely over the other and, in theory, the compromises of coalitions have a better societal outcome than the extreme views one party or the other might hold on a certain issue.
I'm not sure why the popular vote is an issue here. Every democracy has a system for aggregating votes to parliament seats and the transmission is never 1:1.
In this case:
Votes for parties that don’t enter the Bundestag (e.g., those below the 5 % threshold) are not counted in seat allocation, making the share of seats for CDU + SPD higher than their raw vote share. Seats are redistributed proportionally among the parties that did enter parliament.
I don't see much of a problem.
The claim that a fragmented territory with a multitude of small democracies is a good thing is a libertarian pipe dream. This view is quite frankly absurd considering that every government task is subject to economies of scale: defense, police, health insurance, social security, pension systems, roads, you name it. This is a scenario for winner-takes-all situations between nations, which is a much much worse outcome than even a winner-takes-all situation between political parties.
I believe your view of what democracy is tainted by what USA democracy looks like.
Quite a few countries have more or less successful parlamentary democracies, where winner-takes-all situations are avoided by design. In these, a party rarely has the upper hand and coalitions are the only means of reaching power. The agreements these coalitions forge to govern are a proxy of the compromises all societies have to agree on to function.
A string value in a json config needed to be updated.
On one prod instance, typo while updating the config by hand. Config validation of the software caught it, software stopped with the appropriate error message, a few minutes later we were up and running again.
We introduced work reviews on prod instances (similar to code reviews) after that.
Later, he then wrote a patch script to avoid making that mistake again.
In the json schema definition used in the script, the name of the property had a typo (how it came to be... no clue, copy paste should have taken care of that).
The script was part of a MR, the reviewer missed the typo. We noticed it in staging.
We introduced tests for config editing scripts after that.
And so it went on and on... The problem is not that it happens and we then refine our processes. It is the frequency.