cpinitiative / usaco-guide

A free collection of curated, high-quality resources to take you from Bronze to Platinum and beyond.
https://usaco.guide
Other
1.62k stars 495 forks source link

Internal solutions for USACO problems? #821

Closed dolphingarlic closed 3 years ago

dolphingarlic commented 3 years ago

So USACO problems all have editorials already, but I recently got this feedback on Discord:

pleasepleaseplease add like really nice editorials for superhard silver problems, Im really dying on these and the normal editorials really suck please :pray:

(And when asked about specific problems):

well rn i really dont understand meetings moop and clock tree

How should we approach this? Do we write internal solutions for these problems, or can USACO update their editorials somehow?

SansPapyrus683 commented 3 years ago

Uh... is there anything wrong with writing an internal solution for these problems?

thecodingwizard commented 3 years ago

I think internal sol > update existing USACO editorial. We can copy paste and modify the official editorial if we want (and then just include a citation or something)

dolphingarlic commented 3 years ago

Uh... is there anything wrong with writing an internal solution for these problems?

I just think unnecessary internal solutions are a bit wasteful, but I guess it's fine if the official editorial is actually bad

fishy15 commented 3 years ago

I do agree that having unnecessary internal solutions is wasteful, and the official editorials could simply be linked to. However, there are certainly problems that should have rewritten solutions (notably cowland comes to mind, I am not too familiar with silver editorials however).

An advantage with having internal solutions is that we can update them based on user feedback on what editorials they are finding confusing.

bqi343 commented 3 years ago

Im really dying on these and the normal editorials really suck please 🙏

well rn i really dont understand meetings moop and clock tree

wow I wonder who wrote these??

(but srsly, please be more specific about what should be changed?)

Shad0wSeven commented 3 years ago

image hey that was me :thonk:

I would say certain editorials (no hate to writers) are just like too complicated??? or are too hard to understand I eventually got them but for at least the problems categorized as "Insane" or "Very Hard" internal sols if the external ones are confusing would be nice.

SansPapyrus683 commented 3 years ago

Of course, I 100% agree that some of the editorials are hard to understand.

(but srsly, please be more specific about what should be changed?)

I feel like in the internal solutions, we could add on to the explanations by providing some sort of example.

For example, in Meetings, we could use the sample input and say "Consider the first cow. Notice that [insert explanation here]". I feel like that would be a great improvement.

skittles1412 commented 3 years ago

On a similar note I think the editorial for circular barn gold could be improved. It uses one incorrect, confusing, and ambiguous sentence to explain the core part of the solution (where to find the starting point). Although more explanations, examples, and maybe even pictures could be added on USACO Guide, I feel like incorrect solutions like this one should be changed on the USACO website.

SansPapyrus683 commented 3 years ago

Yeah, and there's a bunch of other solutions that could use further explanation. Perhaps something like a "request internal solution" button along with a form asking for a reason would help alot.

bqi343 commented 3 years ago

There's already a contact us form where you can request an editorial.

thecodingwizard commented 3 years ago

I think walking through a sample input like you mentioned would be most effective in a video solution. I personally think the text editorial is fine as is and does not warrant such changes, though I agree it would be nice if someone were to make a video solution that did contain an example walkthrough.

SansPapyrus683 commented 3 years ago

Well, if no one can do a video solution walking through the sample input, the second best thing would be to just do a text walkthrough.

thecodingwizard commented 3 years ago

unless people have specific requests to revise certain internal solutions, I'll just close this :P