One of the code golf leagues of all time, the ACGA announces its inaugural season to start in Spring 2024. The rules are simple: complete the challenges (all 18 of 'em) for prizes that don't exist and kudos that aren't at all professionally valuable. You could say you'd put the PRO in "PROgrammer" or in "PROduction," but let's face it: those aren't the jokes. These challenges will offer your more lulz than you thought possible which were probably none in the first place.
The easiest way to answer this question is to do what all very online people do, and cite Wikipedia's entry on the subject:
Code golf is a type of recreational computer programming competition in which participants strive to achieve the shortest possible source code that solves a certain problem. Code golf challenges and tournaments may also be named with the programming language used (for example, Perl golf).
Each round will be added to the parent repository that players will fork. Notification of new rounds will be sent when rounds are released and will prompt players to update their fork(s) and provide instructions for how to do so.
| Round Number | Start Date | End Date |
|---|---|---|
Round 1 |
19 January | 22 January |
Round 2 |
26 January | 29 January |
Round 3 |
2 February | 5 February |
Round 4 |
9 February | 12 February |
Round 5 |
16 February | 19 February |
Round 6 |
23 February | 26 February |
Rounds 7-8 |
1 March | 15 March |
Round 9 |
15 March | 18 March |
Round 10 |
22 March | 25 March |
Round 11 |
29 March | 1 April |
Round 12 |
5 April | 8 April |
Round 13 |
12 April | 15 April |
Round 14 |
19 April | 22 April |
Round 15 |
26 April | 29 April |
Round(s) 16-18 |
29 April | 6 May |
Rounds are governed by time, not attempts. As long as your best effort is in by 🕙 23:59 (EST) on the day the round ends, it's the latest entry that counts.
You'll need to
python -m pip install gatorgrade
to get the automated grading system (AGS) that we use to run our tests. Once you've done that, type:
gatorgrade
to run the grader. The score should be the top line in the readout.
You'll need to head to Settings and enable GitHub Actions on your fork. This will run the workflows
already built in the repositories and add your stroke count to the Job Summary for a given GitHub Actions
run.
Nope. The tasks are all made up and the points aren't real.
Only if you want to be laughed at.
For the Open-Rank leaderboard:
Entries for the Open-Rank league close on 22 January 2024.