GopherCon 2015 lightning talk results
Registrations for the GopherCon’s Hack Day talks closed on the 20th of July, here are the results.
Forward
After the popularity of the lightning talk sessions last year, and the huge interest the call for papers received, we expected very high demand for lightning talk slots this year.
Surprisingly, that demand never materialised. However, this is good news, because it means that everyone who registered their interest will have the opportunity to present on stage. Also, due to the lower than expected number of registrations, there was a heavy bias towards the Hack and Tell category, without enough numbers to make up the other two categories.
So, with no need to cater for outrageous demand we’ve scheduled the speakers in the order in which they registered. If you submitted more than one proposal, we’ve listed all your talk titles, it’s up to you to choose which of your proposals you’re going to present.
Finally, all the lightning talks will be recorded and available after the conference.
Speakers
We’ve scheduled three lightning talk sessions with 10 talks each over the course of Friday July 10th. All talks will be held in the Mile High Ballroom. The first session begins at 11:00 and runs through to lunch at 12:30. The second resumes at 13:30 and runs through to 15:00. After a short break, the third session begins at 15:30 and runs til we run out of speakers or we reach end of day.
Session One
11:00 - 12:30
| Name | Title (please pick one) |
|---|---|
| Larry Clapp | Never Type “ls” Again: A web-based Unix/Linux/MacOS shell & editor |
| Ian Eyberg | Compile-Time Code Weaving with Go |
| Joey Geiger | Connection Manager in Go or, dealing with a self created zombie horde |
| Kevin Gillette | Sets and The Universal Type |
| Nathan Davies | Pgbouncer pain, a true story, or Reduce the moving parts |
| Alan Shreve | Lessons scaling ngrok: microservice architecture without the pain |
| Sergey Ignatov | Go IDE Done Right |
| Marty Schoch | Bleve - Full text indexing and search in Go |
| Karan Misra | embd.go |
| Guillaume J. Charmes | Dynamic reverse proxy in Go, or Safe privilege de-escalation in Go |
| Lev Kravinsky | One of Contributing to Congo, or Go for Rubyists, or When did hating on Go become cool? |
Break for lunch
Session Two
13:30 - 15:00
| Name | Title |
|---|---|
| James Bardin | Go Executing Tracing via Source Annotation |
| Zac Shenker | Config Management in S3 |
| Raj J | How I used Go to write a simple and efficient service |
| Nick Sardo | JSONPath - Do you need to json.Unmarshal it all? |
| Brian Hicks | How to compile Go in Docker and still get a tiny container |
| Nick Sullivan | CFSSL: Was it a success? |
| Marc-Antoine Ruel | pre-commit-go: run tests smart: based on dependency graph; fast; as git hooks |
| Katherine Cox-Buday | Gorkin: Cucumber runner in Go. A good thing? |
| Richard Musiol | GopherJS - A compiler from Go to JavaScript |
| Joe Shaw | Galaxy: A Heroku-like micro-PaaS built on Docker |
| Brian Akins | Extending Go Programs: A Few Approaches From the Wild |
Break for refreshments
Session Three
15:30 - til close
| Name | Title |
|---|---|
| Gabriel Aszalos | Scaling Sourcegraph with Go |
| Jeremy Schlatter | How I built a Go debugger using source rewriting |
Registrations on the day
We will be accepting registrations on the day, please come to the side of the stage and speak to the organisers. You will present in the third session once all the registered speakers have given their presentations. Registrations on the day will be handled on a first come first served basis.
The Lightning Talk Rules
Here are a reminder of the rules.
- Talks are 7 minutes each. After that, the mic is turned off.
- You’ll get one warning at the 5½ min mark.
- Slides are allowed, but not required, and you can flip them at your own pace.
- Demos are allowed, but please be mindful of the time and plan ahead for technical issues.
- One minute for questions while the next speaker is setting up (you can use more if your talk ends early).
- You can submit as many talks as you like, but to be fair to others, you can only present one talk.
- All talks must adhere to the GopherCon Code of Conduct