programming

Brian Will makes the case for procedural programming over object-oriented programming, arguing that OOP's promised encapsulation and decoupling are largely illusory. He analyzes real code examples and the problems of tying data to behavior in classes.

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.

A short clip of Casey Muratori from Handmade Hero explaining why he rejects the object-oriented mindset and how to move away from it. It is part rant, part programming philosophy.

Jonathan Blow's hour-long livestreamed response to a RustConf 2018 closing keynote about entity systems in Rust. He argues that index-based entity systems amount to manual memory management that sidesteps the borrow checker, and he talks about friction for game developers.

Tom Scott recounts the worst typo he ever made, a subtle mistake in code with destructive consequences at a previous job. It is a cautionary tale about irreversible operations.

A 10-minute clip from a Jonathan Blow Twitch stream in which he argues that game engines do not really need separate scripting languages. He questions the value of embedded interpreters when the main language can do the job.

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.

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

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.

A one-minute clip of Steve Ballmer explaining IBM's obsession with counting thousands of lines of code (KLOCs) as a measure of programmers. He explains why that metric is useless.