[d1sxeyes]

Fair point, but sometimes, especially with a deadline and a rough idea of how you're going to implement something, it's faster to code something yourself, warts and all, rather than sifting through Github to find ones that look good, cloning, installing dependencies, and checking that they have all the features you need, they work correctly, and that you won't need to familiarise yourself with someone else's codebase quickly enough to fix edge cases.

[rurban]

Well, when I faced a similar problem (organizing large table tennis tournaments) which exceeded the limit of the usual free android apps (max 10 players), I prepared beforehand these two apps.

And in one cases I even needed it then, because too many players showed up. Using a lame closed-source app causes always sweat, so I'm better well prepared.

https://github.com/search?q=swiss+tournament&type=repositori... => 667 results

https://github.com/JeffHoogland/pypair/blob/master/pypair.py uses the exact same format she needed.

[d1sxeyes]

She was a judge, not the organiser, as far as I can tell, although it's great she was able to help, contingency planning is something more for the event organiser. The contingency planning seemed to have been MTGMelee, with untested further contingency options of Challonge and YuGiOh!, all of which failed.

You were able to find one that looks like the format she needed, but what would you have done if it doesn't? Or if it's broken?

It takes time to review > 300 lines of code, and she was on the clock. Even if she is able to read 1 line per second, it would take her five minutes just to read through the code, without downloading it, running it, testing it.

I absolutely agree that there should be a review of the contingency planning, but having more confidence in your coding abilities than your ability to search Github effectively is not necessarily wrong.