Competitive Programming: Accepted at the Buzzer Hats

Competitive programming has its own scoreboard, vocabulary, and reasons to celebrate. ICPC regional rules put three contestants on a team for a contest that typically lasts five hours. Teams rank first by problems solved, then by total time; rejected attempts add 20 minutes only when the problem is eventually solved, with compilation errors excluded. A small verdict can carry a lot of weight. Codeforces adds another layer of suspense: its help pages distinguish pretests from final testing, describe points for successful hacks, and acknowledge different scoring formats. That is the world behind the pretest complaint, the rating-over-endorsements comparison, and the grandmaster ambition in this collection. The time-limit nightmare belongs to program execution, as the verdict definitions explain, rather than the moment the contest clock runs out. Then there are the balloons. Harvard's account of the 2025 ICPC finals describes balloons at tables indicating solved problems, giving the celebration a very particular shape. These hats put that reward beside the competitive programmer badge and established apparel phrases such as Expert On Codeforces and AC in one go. Pick the rating flag, the balloon confession, or the time-limit nightmare for your own contest-day wardrobe.