A good reason to deny meetings. No agenda - no meeting. :)

Here in Germany we have early elections, because the current government failed due to internal disagreement. And as usual, each of them promises everything you can think of, just to get some more votes.

Lucky me, we have "die Partei" (yes, that's there literal name), who are basically just trolling everyone. Just checkout out their party platform for this election: https://www.die-partei.de/btw25/ (can be easily translated).

And yes, they can be elected. :)))

If you are reviewing pull requests to your code base, what aspects do you focus?
I am asking, because a colleague of mine most of the time complains about minor code style issues, like the following:

"why is that method static, it belongs to the object. I am not used to static methods, please adjust"

"the methods are not arranged in a standardized breadth-first order"

"Please use that other kind of initialization..."

Those nit-picks make me crazy sometimes. Is it just me?
I mean, her reviews also contain valuable content, but those small complains about coding style feel like "I did not found anything else but I have to". ^^

Me being confronted with multi dimensional data in CSV files...

I only write documentation, so that I can tell others to ReadTheFuckingManual some day!
:)

Damn, I hate it if asking a question leads the counterpart to telling long background stories. Please: Just. Answer. The. Question.

I have my own thoughts and reasons why I ask and don't need your interpretation of my question. If I was not specific enough, please ask back.