Thanks for the pointers! I learned a great deal.
OkOk (nice to learn that try blocks take care of the closing by default!)mPoint is short for matcherPoint. I see a lot of Pattern p = … and Matcher m = … so this seemed like a suitable naming - switching.OkI’ll think about what would be logical to split into classes/methods and with that as base maybe try some GuardClause conversions of remaining superfluous nesting.Ok. If I understand correctly, e.g. lines 25-33 should be put outside the if-bracket. I guess this is readability related / common praxis more than computationally significant?
something happened seems like a question longing for a technical answer, I’m not sure what info you are after. But cities is neither really really cities - it can be a club or a city or whatever the results uploader decides to put there. I have seen up to three words used on occasion; however mostly it is null. Let’s call it a property of the participant that in theory can be anything between zero and n strings. Heck, come to think of it, there might even be integers there
There will not be a + sign though. Yes?
Course & letter
is the official naming, where the letter stands for level of challenge
in alphabetically ascending order. If you’re feeling invincible, run the toughest Course A.
A: 100, 95 and 90 for top-3, then -2points per place, down to a minimum of 1point/participant
B = 0.88*A rounded to even numbers, down to a minimum of 1point/participant
C= 0.77*A rounded to even numbers, down to a minimum of 1point/participant
Why are two…
Oops, because of my manual summary mistake. This is what it would look like on file;