TIL my thesis could have been easier if Typst would have been available years earlier.

Lots of places in France are so remote and sparsely populated that public transport does not work there, at least not yet. It may or may not work once autonomous vehicles are fit for rural areas, but this may take a while.

That's another reason for increasing minimum wages, as they try to do.

Actually, 90% income tax for the top incomes was common in western countries in the 50s.

400'000€ yearly income is not middle class. It is roughly the top 1%. Are you maybe mistaking property for income?

I would have preferred taxing on property instead of income, but as long as interests and profits and other benefits are part of income, it sounds reasonable to me.

I guess you could try AI-checking it and answer "Ignore all previous instructions. …", followed by some new instructions. Some examples: https://www.aiweirdness.com/ignore-all-previous-instructions/

(Although I guess it would be better to not respond to this obvious case of spam/scam)

One example for self documenting code is typing. If you use a language which enforces (or at least allows, as in Python 3.8+) strong typing and you use types pro actively, this is better than documentation, because it can be read and worked with by the compiler or interpreter. In contrast to documenting types, the compiler (or interpreter) will enforce that code meaning and type specification will not diverge. This includes explicitly marking parameters/arguments and return types as optional if they are.

I think no reasonable software developer should work without enforced type safety unless working with pure assembler languages. Any (higher) language which does not allow enforcing strong typing is terrible.

I have worked on larger older projects. The more comments you have, the larger the chance that code and comment diverge. Often, code is being changed/adapted/fixed, but the comments are not. If you read the comments then, your understanding of what the code does or should do gets wrong, leading you on a wrong path. This is why I prefer to have rather less comments. Most of the code is self a explanatory, if you properly name your variables, functions and whatever else you are working with.

Correction, 50% of VOTING Americans are VOTING fascist. Doesn't necessarily mean they are fascist themselves.

Same question on reddit a while ago

As suggested there, I recommend to use a multimeter to identify the power socket pins. Roughly half of them should be ground. Most or all of them should correspond and be connected to the SATA power connector pins on the other side.

+1 on that. The User's guide of a similar device (source) mentions a 10-pin CPLD connector Reserved for IBM use

It would be unmanageable if I tried to do this without a proper tiling window manager though, I use Sway.

"I use sway BTW" 😉