The plot has already being discussed at length. I want to talk about quidditch.

Quick recap, in quidditch, scoring goals scores 10 or 20 points, catching the snitch scores 150 points, and ends the game. This effectively means that the only way a team can catch the snitch and lose is if they are over 150 points behind.

As a result of this, logically the seaker should not attempt to catch the snitch if the score is this unfavourable, meaning the game is always decided by the seaker, and nothing anyone else is doing remotely matters. Remember also we see the audience is rarely able to see what the seeker is doing from the stands.

Now you may say “what about the world cup in book 4, Krumm catches the snitch and still loses”. This can only be attributed to Krumm got mad at his team, or maybe bored, otherwise he should just wait and see if his team can score a goal or two. If the other team’s seaker catches the snitch you lose anyway, so why even try until it’s going to win you the game? Maybe he was showing off to Hermione.

We also know for certain that this happens very rarely, as the odds given to the twins by Ludo Bagman are very high, leading to a big payout. Therefore quidditch is entirely decided by something that happens well out of sight of the audience, and would be terrible to watch or play.

As an aside, the rules around catching the snitch leading to a draw are never mentioned, but I assume they have some penalty shootout system

That’s why showing the expected outcome is also very important. It can feel very verbose, but the number of times I’ve been unclear as to if something worked because the documentation goes on immediately to the next step without demonstrating the success/failure states is extremely frustrating.

It definitely can, but it won’t if you’re looking for it

Binary Large OBject

Basically any binary file, often objected to in open source repos because of the lack of source and ‘openness’. See also the recent xz backdoor.