Scripting Games

Scripting Games 2014 – event submission tip

Richard Siddaway
1 min read
Share:

I’ve testing out the judging system using the practice event and one thing jumped out at me.
It was a lot easier to understand the entries for those teams that included a transcript of their entry.
I would very strongly recommend that you include a transcript of your entry running. As a minimum I would recommend that you include:

  • the solution running - show each type of input required by the scenario (pipeline, single values, file etc)
  • if parameter validation is asked for - show that in action
  • show error handling in action if you can
  • show the partial contents of any output file
    Transcripts make for happy judges. You want your judges to be happy don’t you…

Related Articles

Mar 18, 2018

Iron Scripter Preludes and Main Event: Rules and Info

Information is now available at IronScripter.us for the at-Summit events, and participants are advised to refresh themselves on the Rules.
Participants attending Summit should begin choosing their faction and getting to know their teammates in the faction-specific channels of the DevOps-Summit Slack team (open only to attendees and alumni).
Participants hoping to participate remotely may wish to start choosing a faction and finding a way to get in touch with them. The Faction Discussion may be a good way to do that.