In general you are right, I expect something like this to appear in the future and it would be cool.

But isn't the criticism rather that there are too many (as you say repetitive, not relevant) events - its not like there are cool stories emerging from the underlying game mechanics anymore ("grand strategy") but players have to click through these boring predetermined events again and again.

You get too many events, but there aren't actually that many different events written, so you repeat the same ones over and over again. Eventually it just turns into the player clicking on the 'optimal' choice without actually reading the event.

You could mod the game with more varied events, which were of course AI generated to begin with. Bit of an inception scenario where AI plays an AI modded game.

The other option is to have an AI play another AI which is working as an antagonist, trying to make the player fail. More global plagues! More scheming underlings! More questionable choices for relaxation! Bit of an arms race there.

Honestly I prefer Crusader Kings II if for no other reason that the UI is just so brilliantly insanely obtuse while also being very good looking.

Well one can only hope so. It has maybe 2 good years left, would be nice to get a new one at some point.

This was such a relieve for us. Looking back its unbelievable how much combined time we wasted complaining about and fixing formatting issues in code reviews and reformatting in general.

With clang-format & co. on Save plus possibly a git hook this all went away. It might not always be perfect (which is subjective anyway) but its so worth it.

Its also faster when used via Remote Desktop, VNC etc. so still doing it for these reasons.

Wondering whether we will see some combination with Cyc at some point (which tried to solve the „encoding of the world“ problem)

After Doug's recent passing, I sincerely doubt it.

There should be SOPs in place for each "expected" issue so people know what to do. Its not like you (should) start debugging and deploying stuff in the middle of your on-call shift anyway. Its not 100% for sure but in the normal case this should be fine.

At first glance this seems like a healthy attitude (and probably is)

On the other hand this spaghetti stuff usually comes back to them in form of new (bug) tickets or even worse on-call alerts. Then they (or some other poor soul) has to deal with it again.

It's a false dichotomy. Software engineering skills and workaholism are independent axes. There are people who work 80 hours a week and write poor code. There are amazing coders who go home by 5:00 on the dot and spend their evenings with their family.

If a product is successful, eventually the tech debt price will have to be paid, but that tech debt is just as often (more often, in my experience) generated by "rockstars" burning the midnight oil to ship a prototype than "bad coders".

Well then let them do it. The more interesting part is the "forcing others to do it" or "being forced by others to do it". The individual should be able to make this decision. But we both know thats not how it works.

Dry cooling towers do exist (though I am aware they also have disadvantages).

Same. I switched from Android (Sony xperia compact series) to a Mini 13 and while it took a while to get used to iOS its just great. A pity they discontinued it, I intend to keep it as long as in any way possible (i.e. until apps don‘t support the then final iOS anymore)