source code

Kaze Emanuar explains how he rewrote and optimized the Super Mario 64 source code so it runs far faster on real N64 hardware. He covers performance bottlenecks and fixes in detail for his ROM hacks.

A reverse engineer walks through fixing a ten-year-old bug in Guitar Hero III without access to its source code, using a disassembler and decompiler. It is technical but explained step by step.

A short video that reads out comments from the leaked Team Fortress 2 source code to show the frustration of Valve's programmers over time.

Bryan Cantrill's talk on corporate open source anti-patterns, first given at FISL 2012 and again at the Liferay Symposium. He lays out the mistakes companies make when open sourcing code, such as announcing future open sourcing, and discusses licenses.

Paul Irish walks through the jQuery source code and shares ten lessons and interesting techniques from it, aimed at JavaScript developers who want to learn from a widely used library.

The first lesson of Uncle Bob (Robert C. Martin)'s "Coding Better World Together" series. It makes the case for clean code and for treating software craftsmanship as an ethical and professional responsibility. It runs about 109 minutes.

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.

A dotJS 2012 conference talk by Fat (of Twitter Bootstrap fame) on what open source really means and why maintainers feel guilty about it. It covers the obligations, expectations and burnout that come with releasing popular open source software, delivered with humor.

8-Bit Show And Tell walks through the BASIC source code of the original Commodore 64 Sid Meier's Pirates!. It covers bugs, quirks and traces of abandoned features and scenarios left in the code.

A DevOps YouTuber tests GitHub Copilot on a range of Leetcode problems and finds it solves most immediately, with a few needing tweaks and some far off. He concludes it would outperform him in a FAANG-style interview.

Blizzard's Timothy Ford explains in this 2017 GDC session how Overwatch uses an Entity Component System architecture for layered gameplay. He also covers its server-authoritative netcode with client-side prediction and how they keep the game responsive and fair.

SethBling uses Super Mario World glitches to inject and run Flappy Bird code on an unmodified SNES, entering it purely with controller inputs. It was the first time a human completed this kind of exploit by hand.

Casey Muratori shows how typical 'clean code' object-oriented patterns can cost large factors in performance. He benchmarks them against simpler data-oriented code.

CGP Grey explains that postal codes are routing instructions for mail rather than geographic regions. He looks at the quirks and problems this causes.

A tool-assisted speedrun of Pokemon Yellow by MrWint that uses arbitrary code execution to push Game Boy hardware to its limits. Through crafted inputs it injects code and ends up running other programs, such as Tetris, inside the game.

3Blue1Brown's discovery-oriented introduction to error correction codes, building up Hamming codes from the puzzle of locating a flipped bit. It explains the parity-check idea and why it is so efficient.

MattKC fits a playable Snake game into a QR code by writing tiny x86 machine code and patching the ZBar scanner so it can run the decoded data.

OpenAI's 2021 live demo of Codex translating natural language into code, from Hello World to building a game and a Microsoft Word plugin.

Ned Batchelder's PyCon 2012 talk gives a quick overview of what Unicode is, then focuses on what a Python programmer needs to handle text correctly. It presents the 'Unicode sandwich' strategy: decode bytes at input, work with Unicode internally, encode at output.

A short 1966 propaganda interview clip in which Jeremiah Denton, a US prisoner of war in Vietnam, blinks the word TORTURE in Morse code. Naval Intelligence later decoded the message.

Veritasium builds a QR code by hand to explain how it works. It covers the history of Morse code and barcodes, how QR codes encode data, why damaged codes still scan, and how safe they are.

A WSJ investigation by Joanna Stern into iPhone thieves who watch victims enter their passcode, then use it to lock them out of Apple accounts and drain bank and payment apps. It explains how the thefts work and how to protect yourself.

A sketch from the Seattle comedy show Almost Live! in which Pat Cashman plays a US Bell rep explaining the new 425 area code. It first aired in 1997.

TED curator Chris Anderson interviews Linus Torvalds about his personality, his engineer's pragmatism, and the creation of Linux and Git. Torvalds also discusses taste in code and why he open sourced Linux.

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.

David Heinemeier Hansson's opening keynote at RailsConf 2019 argues against the expectation of payment for open source work, drawing on his experience releasing Rails. It also includes lighter asides about the industry.

Elm creator Evan Czaplicki's 2018 Elm Europe talk on how to define success for an open source project and language community. It argues against judging projects by GitHub activity and touches on community expectations.

Robert 'Uncle Bob' Martin speaks at Yale School of Management about clean, well-written code and what makes good software development. The talk covers his views on OOP, architecture and professional practice.

Michael Feathers' GOTO Chicago 2018 talk on reducing error checks and conditional logic in code. He offers a framework for handling errors and decisions at the level of code and architecture.

Evan Czaplicki, creator of Elm, gives an elm-conf 2016 talk on the non-code side of building a language. It covers the philosophy behind Elm's development approach, including batching work and the priorities of different language communities.

Daniel Stenberg's keynote at FrOSCon 2025 on AI slop attacks on the curl project, with examples of bogus AI-generated security reports. He discusses the toll on maintainers and why various countermeasures don't fit the project.

A long Tsoding Daily programming stream in which he implements hot code reloading in C by loading a dynamic library at runtime without stopping the main program. It also touches on migrating struct versions across reloads.

A HOPE XI talk on programming by voice with open source speech recognition. The speaker writes Linux systems code by voice and describes building custom voice grammars as an alternative to the keyboard for programmers with repetitive strain injuries.

Greg Kroah-Hartman's Linaro keynote on contributing to the Linux kernel, explaining why maintainers prefer upstreamed code and how they view contributions.

Tom Scott explains for Computerphile how Unicode and UTF-8 grew out of messy older character encodings to become the web's standard. It covers why the design works and how it handles worldwide text.

A DEF CON 29 talk by Richard Henderson about encoding the EICAR antivirus test string into QR codes and barcodes and scanning them at real systems. Many systems that do not expect such input misbehave or collapse, including a parking garage system.

Rachel Potvin describes the scale of Google's codebase and its custom monolithic source repository. She explains the reasons for the monorepo model, the tooling that makes it workable, and its tradeoffs.

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.

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.

Donnie Berkholz of RedMonk gives a Monki Gras talk arguing that abusive, toxic contributors damage open source projects. He makes the case for removing them from communities.