software projects

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.

Zack Freedman gives advice on why makers fail to finish projects, including scrapping bad ideas, showing work publicly and writing a plan that keeps projects fun. It is aimed at hardware DIY but generalizes.

A Vox explainer on why California's high-speed rail project is years late and far over budget, with only a few concrete structures built by 2022. It covers the political, legal and routing challenges behind the delays.

Tom Scott explains for Computerphile why handling time and timezones in code is so hard, walking through a simple web app that computes how long ago something happened. It covers the quirks of timezones and calendars and ends in an exasperated rant.

A short animated simulation comparing how Multics and Unix were developed, showing why Unix's small composable programs and pipes gave it a efficiency advantage. It frames Unix as a moonshot achievable by a small team.

Tantacrul explains how he and engraver Simon Smith designed the free music notation font for MuseScore 3.6. It draws on the history of the SCORE notation application by Leland Smith.

Ward Cunningham explains the history and intent of the debt metaphor, which he coined while refactoring the WyCash product. He says debt means code reflecting an incomplete understanding of the problem, not sloppy programming.

CGP Grey's video "Humans Need Not Apply" argues that automation will make a large part of the workforce economically obsolete, much as engines did for horses. It surveys robots and software replacing both physical and mental labor.

Tom Scott explains why electronic voting is a bad idea. Elections must be trusted by everyone and attacks on software scale in ways attacks on paper do not, so open source or blockchain fixes do not solve it.

Tom Scott-style absurdist tour by Tom7 of SIGBOVIK chess projects: a tournament of 30 weird chess algorithms used to rate a color- and piece-blind chess program. Topics include mirrors, arithmetic encoding, perverted game tree search and a diluted Stockfish.

Matthias Wandel tests old and new code on a range of PCs, including a new mini PC, to measure how much faster modern hardware really is. He also shows optimization techniques such as branchless code, with benchmark programs on GitHub.

Vox explainer arguing the two Boeing 737 Max crashes were not just a software bug but the result of a company's drive to beat its rival, with a flawed MCAS design.

Veritasium explains Bayes' theorem with examples and introduces the 'Bayesian trap', where repeated events get mistaken for inevitable ones. It discusses how priors shape our expectations and behavior.

A Kurzgesagt animation on South Korea's record-low fertility rate and rapidly aging population. It explains why a demographic collapse looks hard to reverse and projects the population shrinking sharply by 2060.

BigClive explains why microwave oven transformer projects are extremely dangerous, since the high voltage and high current can kill. He contrasts them with spot welder builds where the secondary is replaced by low-voltage heavy wire.

Professor Brailsford of the University of Nottingham describes how the university set out to print its own mathematics exam papers in the 1980s. The story centers on getting a Mergenthaler Linotron 202 typesetter to work with their own software.

Practical Engineering summarizes the 2017 Oroville Dam spillway failure, explaining the engineering details behind the incident. It also discusses how operators and regulators failed to keep downstream residents safe.