practice

Pete Hunt of Facebook and Instagram introduces React at JSConf EU 2013 and explains its design principles. He argues that separating templates from logic only separates technologies, not concerns, and makes the case for components.

Pete Hunt of Facebook and Instagram presents React at JSConf.Asia 2013, explaining its design principles and why they seemed shocking at first. He argues that React separates concerns rather than technologies, and the talk also announces the React Chrome developer tools.

Joseph White, creator of PICO-8, retraces the design of the fantasy console and how tools can shape and guide creative work. He discusses cozy, constrained design spaces and the influence of user-made cartridges.

Greg Wilson surveys what empirical research actually shows about software development, why we believe it, and how to share that knowledge more widely. It covers evidence on practices such as TDD and design patterns.

Raymond Hettinger's PyCon 2013 talk on transforming code into idiomatic Python through a series of before-and-after refactorings. It shows how to use iterators, dictionaries, named tuples and other language features well.

Felienne Hermans's Strange Loop keynote on the history and pedagogy of teaching programming. She questions exploration-only approaches like Logo and discusses research supporting explicit instruction and rote practice.

Two Google engineers perform a mock coding interview and then discuss best practices for candidates, including asking clarifying questions and communicating while solving.

John Romero's 2016 GDC Europe talk recounts the early days of id Software and the programming principles behind Doom and Quake, including fast iteration and keeping the game bootable.

Erik Meijer gives a provocative talk presenting what he calls a rational alternative to Agile, arguing against Scrum-style practice. He also touches on the tenth-man concept.

Bret Victor's DBX 2013 talk, delivered in the guise of a 1973 IBM engineer with an overhead projector. It surveys forgotten ideas from 1960s and early 70s computing and warns against assuming you know what you're doing.

Tim Ewald's Clojure/conj talk uses furniture making with hand tools versus machine tools as an allegory for software. It explores how automation changes what we make and how we think about our work, and why Clojure's small set of simple tools matters.

Tavis Rudd describes how RSI forced him to program by voice, and shows the Python and Emacs Lisp system he built with voice recognition. A live demo creates and deploys a small system without touching the keyboard.

Dave Thomas, a co-author of the Agile Manifesto, argues at GOTO Amsterdam 2015 that Agile as a branded industry has lost its meaning. He says agile is an adjective, not a noun, and urges developers to reclaim agility.

Mirabai Knight's PyCon 2013 talk on Plover, a free cross-platform stenography engine that lets people write at up to 240 WPM on ordinary hardware, including a demo of coding by steno.

Evan Czaplicki, creator of Elm, examines how programming languages are funded. He looks at where compiler engineers' salaries come from, why Go has about 5 engineers while Dart has about 30, and how this limits language design.

Joe Armstrong, co-inventor of Erlang, gives a funny and opinionated Strange Loop talk on the tangled state of software: build tools, package managers, entropy and the physical limits of computation. He argues for ideas like naming things by content hash and throwing away your first version.

Bryan Cantrill's Monktoberfest 2017 talk on leadership and organizational principles, ranging from the Gettysburg Address to Uber and Amazon. He argues for the difference between principles and values and criticizes vague corporate principles.

Greg Baugues tells his story of living with bipolar II and ADHD as a developer at a Ruby conference. He urges openness about mental illness and explains how to get help and support colleagues.

Emily Shea explains how repetitive strain injury pushed her to program by voice using speech recognition (Talon), and gives a live coding demo. She argues voice-driven development can be pain-free, efficient and enjoyable.

Bryan Cantrill's Monktoberfest 2016 talk on how software engineers pass knowledge down through oral tradition, from folk rhymes to programmer lore and stories like why C lacks a logical XOR. He argues for writing software with future generations in mind.

Evan Czaplicki, creator of Elm, discusses the hard parts of running an open source project: online community conflict, why its patterns arise, and a cultural history of open source. He offers ideas for more civil, productive communication.

Austin Meyer, developer of the X-Plane flight simulator, explains how he was sued by a patent troll over a trivial claim about an app's license server. He walks through how the shell-company litigation works and why ignoring the suit makes things worse.

Chris Granger, creator of Light Table and the Eve language, gives a Berkeley data science lecture on what computation and programming might look like in ten years. He covers the path that led to Eve and ends with demos.

Brian Fitzpatrick and Ben Collins-Sussman argue that the 'genius programmer' ideal harms collaboration. They advocate trading ego for growth, sharing work early, and understanding how tools shape social behavior.

Jeremy Howard defends Jupyter notebooks as a serious development environment, especially when paired with nbdev. He responds directly to Joel Grus's talk about why he dislikes notebooks, and contrasts REPL-style and notebook-style work.

Steve Yegge records himself working in Emacs and shows off about a dozen features in a roughly 45-minute screen capture. It is an informal, enthusiastic tour rather than a structured tutorial.

Brian Will follows up his earlier anti-OOP video by walking through four short code examples, including Java code in the style of Uncle Bob, to show how object-oriented design complicates simple programs. It argues that OOP hides and scatters state and adds needless indirection.

Nickolas Means recounts the 1979 Three Mile Island accident minute by minute, from the control rod insertion to the operator's decision to switch off emergency cooling. He argues that finding systemic causes is more useful than blaming individuals.

Elm creator Evan Czaplicki's talk on how a file grows and when to split code up. He argues for keeping code in one file until it hurts and warns against premature extraction.

Nickolas Means tells the story of United Airlines Flight 232, which lost all flight control yet saved more than half its passengers. He draws lessons on teamwork, crew resource management and leadership for software teams.

Kevlin Henney's GOTO 2018 talk argues that much of what looks new in software is a recycling of concepts with long histories. It draws on history to show the slow, steady current beneath constant churn in frameworks and trends.

Rob Landley compares Toybox and BusyBox and surveys options for embedded system command-line tools, including GNU. He also tells the story of leaving BusyBox, Toybox becoming Android's command line, and licensing.

Glenn Vanderburg argues at Lone Star Ruby Conference 2010 that university-style software engineering does not work, and asks what real software engineering would look like. He revisits the waterfall model and what engineering means in other fields.

A demo of writing technical documents in Emacs Org mode using org-babel, so that code blocks and generated content stay consistent when things change. The author shares the demo files and his dotfiles.

Timothy Daly, an original author of the Axiom computer algebra system, talks about turning a large Common Lisp codebase into a literate program. He argues code should be written as readable manuals, and the talk was given at Write the Docs 2013.

Gabriella Gonzalez argues that developers misunderstand marketing as deception or hype, and applies the technology-adoption ideas of Crossing the Chasm to Haskell. She looks at what keeps Haskell from reaching mainstream programmers and what a community can do about it.

Patricia Aas's EuroBSDCon keynote is about ethics for people who build software, covering how the tech industry got to its current state and what engineers can do about it. It steps back from technical detail to the bigger picture.

Emily Shea, a Fastly engineer with repetitive strain injury, describes using voice dictation as her main way of programming. She covers homophones, custom vocabulary and building her own voice commands to write Perl.

A podcast episode of Arrested DevOps with Andrew Clay Shafer and Bryan Cantrill, featuring Cantrill's rant on integrity in companies and technology.

LearnCode.academy presents a roadmap of web development technologies to learn in 2016 and 2017, spanning front-end, back-end and DevOps tools.