You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
First off, I had a blast judging @ HackGT 5, thanks for inviting me! One thing that a few of us judges were discussing was the "skip" option when checking in at a project table. During orientation, it was said to use that option if nobody was at the table to give us a new project to judge. However, there were many times when a project was already in demo for either another judge or other students that it would have been nice to "skip" to another project instead of waiting - but nobody wanted to risk flagging a project as not being present by hitting "skip" since we weren't sure what the effect would be.
That being said, maybe a better explanation of the impact on "skipping" a project (and maybe a reminder onscreen like the great voting prompts re scale points), or an additional option for passing over a project that was represented but already engaged?
The text was updated successfully, but these errors were encountered:
First off, I had a blast judging @ HackGT 5, thanks for inviting me! One thing that a few of us judges were discussing was the "skip" option when checking in at a project table. During orientation, it was said to use that option if nobody was at the table to give us a new project to judge. However, there were many times when a project was already in demo for either another judge or other students that it would have been nice to "skip" to another project instead of waiting - but nobody wanted to risk flagging a project as not being present by hitting "skip" since we weren't sure what the effect would be.
That being said, maybe a better explanation of the impact on "skipping" a project (and maybe a reminder onscreen like the great voting prompts re scale points), or an additional option for passing over a project that was represented but already engaged?
The text was updated successfully, but these errors were encountered: