What I Wish I Had Known Before Scaling Uber to 1000 Services • Matt Ranney • GOTO 2016

What people said

jppope · 2018-07 · Recommendation

1) Do not attempt to live code. change your code via version control, build small videos, copy and paste... whatever you do... do not try and live code 2) Read "The presentation secrets of Steve Jobs" ... its not really about Steve Jobs so much as its about how to be a great presenter. 3) building or writing a talk is significantly less important than the delivery... which means that more of your time should be spent on how to deliver the speech (recording I find is the best way to practice) 4) Pick a single thing and do it well, do not attempt to put too much into a talk or tackle something massively complex. 5) Make sure that everyone is walking away with something they can actually use. This doesn't require it be a hard skill... "Soft" or philosophical utilities are just as good 6) Have Fun and be funny... Speakers have a tendency to want to show off the size of their intellect, and the level their competency- having a speech be entertaining is way way more important. 7) DO NOT READ FROM YOUR SLIDES. know your shit. slides are supplementary Extra Credit. Here's a collection of some fantastic technical speeches: * [LINK] * [LINK] * [LINK] * [LINK] * [LINK] * [VIDEO]

Read the original HN comment ↗

kartD · 2017-09 · Recommendation

Little drunk so bear with me :) Rich Hickey: Clojure concurrency[ [LINK] ] Keynote - Rust: confident, productive systems programming by Aaron Turon [ [LINK] ] RustConf 2016 - A Modern Editor Built in Rust by Raph Levien [ [LINK] ] Microservices at Netflix Scale: Principles, Tradeoffs & Lessons Learned[ [LINK] ] What I Wish I Had Known Before Scaling Uber to 1000 Services[ [VIDEO] ] Dynamic Code Optimization and the NVIDIA Denver Processor [ [LINK] ] * if you can get anything on Apple's Ax series that's even better

Read the original HN comment ↗

smcl · 2016-10 · Recommendation

Joking aside I enjoyed that video ( [VIDEO] - for those who didn't see it), the presenter was pretty honest and way more open than I expected. I'm just so curious how those services break down - if it's genuinely on the "lstrip as a service" level or whatever, whether that's "1,000 services" figure was actually a relatively simple API with 10 versions at various levels of deprecation, whether he meant it was 1,000 different service endpoints (250 services each with POST, GET, PUT, DELETE) or what. I want to know more basically :)

Read the original HN comment ↗