Skip to content

Instantly share code, notes, and snippets.

@carols10cents
Last active August 29, 2015 14:08
Show Gist options
  • Select an option

  • Save carols10cents/70596c00b88fdf33d188 to your computer and use it in GitHub Desktop.

Select an option

Save carols10cents/70596c00b88fdf33d188 to your computer and use it in GitHub Desktop.
Workshop ideas

What makes a good (rust) workshop?

  • Make something real-ish, nontrivial
  • Demonstrate testing
  • Demonstrate a data structure
  • Demonstrate SOLID principles
  • Clear steps
  • Little victories - small rewards to keep you going
  • Pick a good scope

What makes a bad workshop?

  • Trivial overused problem examples like FizzBuzz or the bowling kata or GOL
  • Just covering syntax
  • Too big of a scope/too much magic => people don't really learn
  • Too trivial of a scope => people don't feel accomplishment

What would you expect to get out of a half day workshop on rust?

  • Be able to write simple scripts in rust
  • Have the knowledge to move on to more advanced things without too much frustration
  • Know if/why I should keep learning rust

Ideas

  • Provide tests, workshop is about getting them to pass?
  • Emphasize the things about rust that are unique/less common in PLs
    • compiletime errors that would be runtime errors in other langs
    • type inference
    • pattern matching
    • cargo
    • ownership

Stuff to provide

  • binaries
  • cheat sheets (syntax, common errors)
  • code to start from
  • lists of resources for use during/after
  • slides

Advice

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment