Keynote: What Happens to Everyone, When Everyone Learns to Code?
summary
A practical verdict: the claim is that Rails site building and a few cheap services let a nonexpert ship real products — a WordPress blog is replaced by a handbuilt Rails site, locomotive CMS help arrives by Skype, and a people.ext file post lands on Hacker News with Tim O’Reilly praise. Tools named: Flatiron, General Assembly, Codecademy, Chris Pine, Skillshare, gems, GitHub, localhost:3000. Surprising data: 129 million search hits for “should everyone learn to code” and the 12‑week/$80,000 bootcamp claim. Friction points: hostile Stack Overflow responses, missing docs, empty READMEs, and fragile gems.
AI-written summary · about
chapters (5)
- 0:00Start
- 5:37FACT: "EVERYBODY SHOULD LEARN TO CODE"
- 8:49I'VE BEEN WORKING ON IT, TOO
- 26:29SO WHAT DOES THAT MEAN FOR YOU?
- 29:13MEET THE NEW PRODUCT TEAM.
related talks
29m“WTF does run mean?” & other adventures in teaching others to code
35mWhat I learned my first year as a full-time programmer
56mKeynote: Rethinking Computer Science Education
30mThe How and Why of Ruby
01h 18mKeynote: '...then what?'
26mTeaching Ruby for fun and profit
26mWe are Hacks and Have Been Stealing Code for Years...
33mUrban Legends: What You Code Makes You Who You Are
