Skip to content

Latest commit

 

History

History
81 lines (64 loc) · 3.87 KB

schedule-1803.md

File metadata and controls

81 lines (64 loc) · 3.87 KB

Lightning Talks ⚡

Overview

  • Everyone in Module 1 is required to give a lightning talk.
  • A lightning talk is 5 minutes long. We'll time you, and we will have a cut off at 5 minutes. We suggest you run through your talk at least once to make sure you have enough time to cover the content!
  • Presentations are in front of the class.
  • You may select a topic from the list provided below.
  • If you'd like to propose an alternate topic, let instructors know. Alternate topics require instructor approval.
  • Topics are first come first serve basis.

Picking a Topic

  • You don't need to be an expert on a topic. You can do the research and become expert enough to deliver a valuable talk. This is a great opportunity to learn about something you're curious about.
  • A talk needs to teach something of value to the audience.
  • A talk needs to be at an appropriate level for the audience, not too basic and not too advanced.
  • A talk needs to have a message, not just a subject. "Introduction to HTML Canvas" is boring, "Why You Should Use HTML Canvas" has a message.

Topic Selection List

- Megan Haubelt: CSS relative units of measure: ems, rems, percentages, viewport measures
- Arram: Javascript `this` binding
- Kent Huntsman: Javascript function prototypes
4.  jQuery chaining - the good, the bad, the ugly
- Keeliana - Web scrapers - the what, the why, the how
6.  Accessibility do’s and don’ts and/or deep dive
- Joel O'Connor: CSS positioning - all the techniques, pros/cons, results
- Kylee W: Media queries - screens + beyond
9.  Javascript - closures
10. Object Oriented Programming
- Marika: What is this VIM you speak of?
12. Client side security + hacking
13. ES6
- Dave Stonecipher: D3 library
- David Dunn: HTML Canvas
- Alex Bruce: SVGs - all about them, how to use them, when to use them
17. Acceptance testing - what and why?
- Brian Weikel: CSS optimization - easy wins and gotchas
- Todd Ayres: React - what and why?
- Laura Miller: Front End Hip - how to stay in the know on all the things
21. Pairing approaches - all the types and pros/cons
- Chris Boylen: Tips for crafting your “Developer Identity”
23. Team collaboration: github/PR etiquette, good workflows, best practices
- Gavin Love: Breaking the problem down + best pseudo coding practices
25. WTF Webpack? And why do I care?
- Megan Haubel: CSS Styleguides
- Andrew James: Linters - what, why, how, types?
- Tory D: Take your `git` foo to the next level
- Brian Tiedt: Algorithms or die - top algorithms programmers should know
- Jesse: Hacking the FE interview
- Kevin Krom: Who want's to be a ScrumDog-Millionaire? The benefits of Scrum Methodology
- Jeremiah: Building a Website in Layers: Leveraging the Z-Index and Opacity for Visual Interest

How To

  1. Fork this repository
  2. Edit the schedule-1708.md file by inserting your topic next to your name. Presentations start at the beginning of the allotted block in the calendar and we'll roll through each presentation.
- Penelope: History of Women In Tech
  1. Submit a Pull Request to this repository (not your forked repo), titled like so: FirstName LastName: Title of Talk
  • Note: We review submissions based on when pull requests are submitted. You may not see that a topic has been taken if we have not yet merged an earlier pull request to master. We'll let you know as quickly as possible if your proposed topic is already taken.
  1. At some point before the day of your lightning talk, touch base with your instructors to run through your content. You are responsible for reaching out to schedule this. It is not required to physically meet (unless you'd like) - An outline of your talk via Slack is sufficient for approval.

Resources