software licensing

A ten-minute clip from Jonathan Blow's talk on preventing the collapse of civilization, arguing that software quality and the knowledge to build it are in decline.

Andrej Karpathy's keynote at AI Startup School laying out software 1.0, 2.0 and 3.0, with LLMs seen as utilities, fabs and operating systems. It covers LLM quirks, partial-autonomy apps and keeping a human in the generate-and-verify loop.

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.

Asianometry examines why Japan's software industry has lagged despite its hardware strengths. It looks at dependence on US software and the low prestige of programming.

Hillel Wayne reports on interviews with 17 people who have worked as both software and traditional engineers. He argues the fields are fundamentally the same and have much to learn from each other.

Internet of Bugs analyzes Cognition's Devin demo frame by frame, arguing the video did not show Devin completing paid Upwork jobs as claimed, and showing what the task required versus what Devin produced.

JPL's David Cummings presents at the 2025 Flight Software Workshop how the team diagnosed and fixed the 2023 Voyager 1 anomaly from billions of miles away. It walks through the flight computer and the memory fix.

Rich Hickey's Strange Loop 2011 keynote distinguishing 'simple' (not intertwined) from 'easy' (familiar or near at hand). It argues that software complexity comes from complecting things and that we should pick simple constructs.

Keith Packard traces the 35-year history of the X Window System at linux.conf.au 2020. He uses X to examine licensing, corporate interests and community dynamics in free software, including Unix workstation vendors and Stallman's influence.

Tantacrul critiques the UX and UI of Steinberg's Dorico music notation software, comparing it with Sibelius and user testing it with real musicians alongside his own attempt to compose in it.

Tantacrul tells the story of Audacity, the widely used free audio editor, and announces his involvement in the project. It includes an interview with the original developers and a look at the software's usability.

Rich Hickey's Strange Loop 2011 keynote separates 'simple' (not intertwined) from 'easy' (familiar or near at hand) and argues that software complexity comes from complecting things. It offers a vocabulary for judging designs and abstractions.

Casey Muratori responds on-stream to a dismissive Twitter post by demonstrating how slow Visual Studio's startup and debugger watch window are, comparing it to much older software and machines. It is a long rant about software performance and bloat.

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.

Naomi Wu visits the Shenzhen offices of smartphone maker UMIDIGI in person to get them to release source code they owed under the GPLv2, and they comply.

Lars Bergstrom of Google presents how Rust improves team productivity beyond safety and speed, with data on rewrites, defects and review. It compares Rust teams to those on legacy native languages and Go.

Robert Wills of TNMoC explains the Apollo Guidance Computer hardware and software, then walks through the Apollo 11 landing procedure step by step, including the 1202 alarms.

Casey Muratori's lecture, originally given at the Technical University of Madrid, arguing that Conway's Law is the only viable candidate for a true law of software architecture. He explains how software mimics the organization over time, using examples like Windows' multiple volume controls.

Tantacrul walks through how the MuseScore 4 team was built and how design decisions were made for the overhaul of a huge legacy notation app. It covers playback and engraving quality improvements.

Part one of Capt. Grace Hopper's 1982 NSA lecture on the future of data, hardware, software and people. It includes her humor, her nanosecond demonstration and views on scaling and resisting old ways of doing things.

Casey Muratori's invited lecture on where bad code comes from, rebroadcast from a Twitch stream. He critiques conventional wisdom such as SOLID and Clean Code and argues about how those habits lead to slow, poorly structured software.

Andreas Kling ports the game Diablo to SerenityOS, his from-scratch Unix-like operating system, using the devilutionX project. The roughly 80-minute session shows what porting third-party software to the OS involves.

Casey Muratori's two-hour talk tracing the history of object-oriented programming back to the 1960s and examining how its ideas, and later entity component systems, came about. It is followed by a Q&A.

Brian Karis's SIGGRAPH 2021 talk explains how Unreal Engine 5's Nanite virtualized geometry works. It covers mesh import, the data structures, streaming, decompression, culling, software and hardware rasterization, and shading.

Casey Muratori's first refterm lecture lays out philosophies of optimization, distinguishing optimization from non-pessimization, which means avoiding needless work. It uses his fast terminal renderer project to show how fast computers really are.

Casey Muratori shows how fast a terminal renderer can run, building a simple reference renderer that handles Unicode and colored text far quicker than Windows Terminal. He argues that common excuses for slow terminals do not hold up.

Casey Muratori's University of Twente guest lecture is a case study in how straightforward code can cut thousands of lines and tens of seconds of runtime down to a few dozen lines running in under a second. It uses concrete examples to show why software is often an order of magnitude slower than it should be.

Joran Dirk Greef's Systems Distributed '23 talk on TigerStyle, the engineering methodology behind TigerBeetle. It covers designing safer systems in less time through up-front design, assertions, and deterministic simulation.

Casey Muratori follows up his refterm proof-of-concept, a GPU-based terminal renderer, with a second part covering memory usage, glyph sizing and correct Unicode and VT handling. It is built to show that a terminal can be fast and correct without heroic effort.

Bruce Waggoner of the Voyager team describes how engineers diagnosed Voyager 1's 2023 loss of telemetry and patched its flight software from 15 billion miles away. The talk covers the spacecraft's architecture and the scarcity of old documentation.

A 49-minute demo of Palantir Foundry by its chief architect. It walks through data integration, ML and AI workflows, analytics, and application building across the platform.

An AdaCore webinar in which NVIDIA engineers explain why and how they adopted Ada and SPARK for security-critical firmware. It covers the business case and the engineering experience of the transition.

A tutorial in the GAS Therapy series showing how to recreate the Teenage Engineering OP-1 and OP-1 Field with free software. It argues you do not need to buy expensive gear to make music.

A short Microsoft promo comparing classic Teams with the rewritten new Teams side by side, claiming faster startup and better performance. The new version is shown taking around nine seconds to launch.

A WSJ interview in which Apple's Craig Federighi explains Apple's CSAM scanning and child-safety features, including neural hashes and safety vouchers, and defends them against backlash.

A 37C3 talk on how a series of Polish electric trains stopped working after servicing by an independent company. The speakers explain how train control systems work and how they reverse-engineered the software lockouts.

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.

Dylan Beattie's NDC London talk on code written for art, fun and curiosity rather than utility. It includes quines, live music programming with Sonic Pi, and a memorable closing.

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.

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.