Programming is terrible—Lessons learned from a life wasted. EMF2012
tef ebooks3 HN recommenders · recommended in 3 months, 2015–2022
talk · intermediate · evergreen · 2015–2022 on HN
Tef's EMF 2012 talk on lessons from a career in programming, a candid and humorous look at why programming is so often terrible. Slides and a draft script are available online.
HN lists it among its favorite programming talks and fantastic technical speeches.
Up next
2 mo on HNHow to Get Your First Customers | Startup School
Y Combinator
2 HN recommender · 2023–2025
9 mo on HNAgile is Dead • Pragmatic Dave Thomas • GOTO 2015
GOTO Conferences
11 HN recommender · 2016–2026
3 mo on HNWhat I Wish I Had Known Before Scaling Uber to 1000 Services • Matt Ranney • GOTO 2016
GOTO Conferences
3 HN recommender · 2016–2023
11 mo on HNHammock Driven Development - Rich Hickey
ClojureTV
12 HN recommender · 2014–2024
15 mo on HNRailsConf 2014 - All the Little Things by Sandi Metz
Confreaks
15 HN recommender · 2015–2025
2 mo on HNBret Victor Inventing on Principle
Luna Programming Language Tutorials
3 HN recommender · 2020–2022
11 mo on HN🚀 TDD, Where Did It All Go Wrong (Ian Cooper)
DevTernity Conference
11 HN recommender · 2018–2024
11 mo on HNBret Victor The Future of Programming
Joey Reid
12 HN recommender · 2017–2026
10 mo on HN"Uncle" Bob Martin - "The Future of Programming"
Paul Stringer's Mobile Tech
10 HN recommender · 2016–2022
10 mo on HNTim Ewald - Clojure: Programming with Hand Tools
ClojureTV
9 HN recommender · 2014–2024
9 mo on HNUsing Python to Code by Voice
Next Day Video
12 HN recommender · 2013–2025
9 mo on HNTransforming Code into Beautiful, Idiomatic Python
Next Day Video
9 HN recommender · 2014–2022
6 comments from Hacker News
That and Hammock Driven Development: link Both of these talks are in my top 5. Edit (okay, here are the other 3): * All the Little Things by Sandi Metz link * Programming is terrible—Lessons learned from a life wasted. ▶ this video * Some talk I saw by Dan McKinley on making Data-Driven decisions. I can't find the original video, but here's a really similar one: link
Rich Hickey - Hammock-driven development: link Brett Victor - Inventing on principle: link Programming is terrible: ▶ this video Dave Beazely - Python concurrency from the ground up (applicable to languages in general, with generator and corourine functionality) link Functional programming, with birds: link Short and classic: Wat link
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 * ▶ this video * link * link
I think it's a rehash (conscious or not) of Thomas Figg's famous "Webapps, or as I like to call them: Skins around databases." -joke that he used in his "Programming is terrible—Lessons learned from a life wasted" talk from many years ago. It's no longer completely true, but honestly it's still kind of true. And I've been making my living writing them for years now ;) [0] ▶ this video
I don't mean to troll, but having ideas is nothing. Of course projects start with ideas but if the creator of the idea didn't pursue given concept - neither should you. ▶ this video
Just the slides do. Maybe he later thought the same and then omitted or replaced that suggestion in his talk. ▶ this video