Video is 48 minutes, and in a format I find very difficult to follow and stay engaged. Here are the bullet points from the slide deck: Who's Johnny? - Can't cr

Video is 48 minutes, and in a format I find very difficult to follow and stay engaged. Here are the bullet points from the slide deck: Who's Johnny? - Can't create something without examples. - Almost never upstream patches to what they use. - Industry's definition of a healthy ecosystem wrapped around "Johnny". Extreme Time Preference. - Problems in software are not 0-60 times. - Optimized for triviality. Can't Hire Out Of This Problem. - We don't know how to interview well. - Many interview practices are odious. "Hire Only The Best." - Complete nonsense. - Nobody can sustain being extremely picky about their hires. - Everybody else "hires only the best". - This isn't a plan, it's a mantra. - There's no competitive advantage here unless you have a lot of money and are willing to churn your hires. - Burn & Churn doesn't select for experienced employees. - Doesn't charm them either. What We're Unwilling To Admit. - Much of our work is boring and easy. - Some find a niche and are not often obligated to skill up. - Might learn new tools, but don't develop in a lasting and general way. Coders Don't Know How To Learn. - Never learned how to learn properly. - Can be difficult to get programmers to eat their vegetables. - Knowing is not the same as ability. Coders Don't Know How To Teach. - Create false narratives around how they learned. - They recommend books, resources intended to project [or increase their own] prestige more than to help the student. Teaching Is A Skill. - Takes practice. - Almost everyone is bad at it for quite a while. - Without expertise, extremely unlikely to be successful. - Students won't tell you they don't understand forever. Teaching: Topics. - They teach topics that have prestige associated with them. - Not covered: skill building. Teaching: Methodology. - Talking isn't very useful. - Dialogues work best as remediation/unsticking. Teaching: Time - Difficult to parachute in for an hour a day. - Can't do much with that time without foundation of work. Software Is Bad At Writing. - Very few books go through substantial review. - Fewer act on it in a meaningful way. Programmers Are Literate But Can't Really Read. - Like not being able to retain a novel in your mind. - Can't incorporate mental model of what they read. - Stunts growth. - Writing checks their knowledge and skills can't cash. - Perpetual rediscovery of idiom. Employers Aren't Doing Their Part. - Expect highly skilled programmers to drop out of the sky. - Substantive on-the-job education or training is rare. Training Makes Business Sense! - Training is software moneyball. - [Photo of a person not recognized by transcriber.] Company Incentives - Programmers (rationally) change jobs. - Companies aren't often keen on investing deeply into training. - Conferences are about it, actually. Training As A Culture. - Wouldn't you rather work at a company that invests in the training of its people? - How much easier would hiring me [be] if your company had an uncommon reputation for internal training and education? Anthony Grafton. - [Photo of a person not recognized by transcriber.] - Recently listened to a talk of his about the history of books, reading, and digitzation. - He has concerns about how people read today. - I share his concerns. - I strongly recommend Grafton's "Codex in Crisis" talk at Google. Programmers Are Illiterate. - It's worse than the situation with books and broader society. - We're an amnesiac culture. Learning To Read Code - [Photo of Haskell Almanac book.] Make A Mess, Clean It Up! - [Photo of a person not recognized by transcriber.] - [URL http www folklore org] [Video from *Defender: 1980 Classic Arcade Game"] Don't Train How You Play. - Train harder, be more focused and structured.