Re: Why are these events?
Posted: May 11th, 2019, 7:13 am
Game On should be an event for Div C, expect you use Unity/Unreal Engine instead of Scratch.
That would never work. Both are far too involved for anything meaningful to be done in an hour.JoeyC wrote:Game On should be an event for Div C, expect you use Unity/Unreal Engine instead of Scratch.
What was the intent of sumo botsEastStroudsburg13 wrote:Not adding any specific opinions about certain events, but I think, with any event, you have to consider both a) the overall intent of the event, and b) how well it rewards competitors for grasping that intent. Some events with great intents end up being much less effective in practice (Sumo Bots comes to mind).
In Michigan, there is an event that has been run as a trial for about 3 years now that's called Source Code, which is an event that uses Python. I don't know how many other states use it, but I find it interesting that it has been a trial for so long.UTF-8 U+6211 U+662F wrote: It's worth noting though that Scratch has a substantially different paradigm than any other programming language I know; personally, I'd prefer if the language were something that looked like Python with optional block dragging for stuff if you want it, but that's just me.
We had something similar in VA called Code Analysis in 2018 that VASO ran in place of Game On. MIT also ran What the Function as a trial this year, which used Python and had a focus on functional programming. Computer science is definitely important enough to merit having a real programming event every year, at least in Division C.SHASO2018 wrote:In Michigan, there is an event that has been run as a trial for about 3 years now that's called Source Code, which is an event that uses Python. I don't know how many other states use it, but I find it interesting that it has been a trial for so long.UTF-8 U+6211 U+662F wrote: It's worth noting though that Scratch has a substantially different paradigm than any other programming language I know; personally, I'd prefer if the language were something that looked like Python with optional block dragging for stuff if you want it, but that's just me.
BrownieInMotion wrote:We had something similar in VA called Code Analysis in 2018 that VASO ran in place of Game On. MIT also ran What the Function as a trial this year, which used Python and had a focus on functional programming. Computer science is definitely important enough to merit having a real programming event every year, at least in Division C.SHASO2018 wrote:In Michigan, there is an event that has been run as a trial for about 3 years now that's called Source Code, which is an event that uses Python. I don't know how many other states use it, but I find it interesting that it has been a trial for so long.UTF-8 U+6211 U+662F wrote: It's worth noting though that Scratch has a substantially different paradigm than any other programming language I know; personally, I'd prefer if the language were something that looked like Python with optional block dragging for stuff if you want it, but that's just me.
I'd also like to bring up Protein Modeling. To be clear, I loved Protein Modeling and think it should stay, but there are aspects of the event that I never really understood why they existed. For one, I really don't see what value actually building a model of a protein has or what the idea behind it is. I'm not trying to be crass--I'm genuinely curious as to why that's part of the event. Does it have to do with MSOE's involvement with the event? Also, all of the MSOE-written tests I took this year were really short, really easy, and asked a lot of biology and not a lot of biochemistry. Why does MSOE write tests for this event if they're not going to be particularly good? Couldn't they just sponsor the event and let tournaments run the event on their own? Protein Modeling was definitely my favorite event to study for this year, but the professionally-written tests were consistently of a poorer quality than the invitational tests I took, in my opinion. Anyways, if anyone can shed some light on either of these details I'd appreciate it haha.
The idea (here's some random stuff - build a tower / bridge / whatever) isn't horrible. The implementation is horrible (it's basically impossible not to see what other teams are doing. It also puts a heavy penalty on making a misstep: you have a limited set of raw materials, and if you do something you regret (folding a sheet of paper that you later decide you wanted to roll into a tube, for example) there's no way to recover, 'cause you can't un-crease your paper.builderguy135 wrote: ↑July 6th, 2021, 12:55 pm [*] Mystery Architecture is a terrible event. It's incredibly luck based and almost impossible to be consistent at. It's frustrating when the event supervisors clearly don't care about the event. So many bad memories.