[rigelbm]

I stopped at "Good Programmers". Seriously though, it would have been perfectly fine to phrase it as "Exploring the correlation between Code Style and Competitive Programming Performance". Everyone knows that competitive programming has constraints (e.g. small time limit, throwaway one-off deliverable, no collaboration) that favours a style of coding that you wouldn't normally find, for example, on a business setting.

It's not clear whether this paper was accepted at the conference, but if it was, it is a testament to the low bar of the examining board. I like to follow the "if you don't have anything nice to say, don't say anything" mantra, but this paper deserves an exception.

[marginalia_nu]

You really should consider reading articles with a more generous mindset, not just stopping at the first ostensible flaw.

[zopa]

You’re saying we should judge things on their substance as a whole, and not by superficial details?

Persuasive! I wonder if we could apply that insight to any other field of endeavor…

[sdf4j]

> You’re saying we should judge things on their substance as a whole, and not by superficial details?

This is literally the goal of the study. Judge programmers based on the superficial details of competitive programming results.

[moffkalast]

Nah, that would never work.

[phonescreen_man]

Everyone knows that competitive programming has constraints

I didn’t know! I’m part of everyone

[z3t4]

Next you will read a paper about something you are not an expert in and will think every word is fact and truth.