This is just like last semester except a bit more technical. It's a chance to learn about more diverse topics that we couldn't cover in class last semester. And it's also a chance to learn something more than the rest of your peers. Enough to teach it to them!
Talks should be 30 minutes long. You can use slides, images, and code samples or demos as needed, but no videos this time. Your talk should answer a few basic questions about your topic:
Thirty minutes is not a long time to learn everything about a topic, so just focus on the basics. I'd rather you give a presentation that teaches a few solid concepts than many shallow concepts.
Two weeks before your presentation date, you need to hand in an outline via Slack. Format is your preference. It should be able to answer your major questions about the topic and provide some insight into how you are dividing your time.
A week before your presentation date, you need to hand in a rough draft of your talk. This may be an overview of your slides and/or your code samples. I want to make sure you're on the right track with the topic. That means I should see rough details for every part of your presentation, not just the beginning slides.
This is your chance to be the expert on something none of us know about. Enjoy it! Help us understand your topic and why we might want to learn more ourselves. And relax!! Since none of us know your topic, we're not expecting anything out of you. So just have fun learning a new thing and sharing it with us!
If you want us to follow along like a workshop, send us install or setup instructions before your talk starts so we can get it out of the way before you get started.
| Criteria | Doesn't Meet Standard | Meets Standard |
|---|---|---|
| Preparation | Outline and initial slides show minimal understanding of material, poor organization, and little to no plan for remaining work. | Outline and initial slides show familiarity with material, clear organization, and obvious plan for remaining work. |
| Content | Content was too basic or askew from our coursework to be relevant. Focused too much on concept or application alone. Incomplete intro to topic. | Content was relevant to our current understanding of programming and served as a good intro to the topic. Good mix of concepts and application. |
| Organization | Content was presented haphazardly, redundantly, or contained gaps between concepts. | Content was presented in logical order with effective transitions. |
| Documentation | Content provided no supporting documentation. | Content was supported with sources and links for further investigation of the topic. |
| Originality | Presentation relied solely on examples found in documentation or articles. | Presentation used some examples from topic's documentation but also created other original examples to show full understanding of material. |