Evidence

Format Online paper / PDF

"Requirements volatility is associated with higher defect density, project delays, cost overruns and significant architectural change"

View Source

Location PART 1 - TONS OF PUNKS, ONE BIG JERK CHAPTER 2: NO MOAT IN BLOAT Code Is Law

Source title Impact of requirements volatility on software architecture - How do software teams keep up with ever-changing requirements?

Source authors Sandun Dasanayake; Sanja Aaramaa; Jouni Markkula; Markku Oivo

Source year 2019

Confidence high

Importance high

Format Online paper / PDF

"David Clark’s 1992 IETF plenary presentation produced the aphorism rejecting kings, presidents and voting in favor of rough consensus and running code"

View Source

Location PART 1 - TONS OF PUNKS, ONE BIG JERK CHAPTER 2: NO MOAT IN BLOAT Code Is Law

Source title RFC 7282 - On Consensus and Humming in the IETF

Source authors P. Resnick

Source year 2014

Confidence high

Importance high

Format Web Page

"David Clark helped lead early Internet development and served as Chief Protocol Architect from 1981 to 1989"

View Source

Location PART 1 - TONS OF PUNKS, ONE BIG JERK CHAPTER 2: NO MOAT IN BLOAT Code Is Law

Source title David Clark

Source authors MIT Computer Science and Artificial Intelligence Laboratory

Source year 2023

Confidence high

Importance high

Format Online paper / PDF

"Generative AI can compound metacognitive difficulties for some struggling novice programmers"

View Source

Location PART 1 - TONS OF PUNKS, ONE BIG JERK CHAPTER 2: NO MOAT IN BLOAT No Magical Wand

Source title The Widening Gap: The Benefits and Harms of Generative AI for Novice Programmers

Source authors James Prather; Brent N. Reeves; Juho Leinonen; Stephen MacNeil; Arisoa S. Randrianasolo; Brett A. Becker; Bailey Kimmel; Jared Wright; Ben Briggs

Source year 2024

Confidence high

Importance high

Format Online paper / PDF

"In Vessey’s study, expert programmers adopted a system view during debugging more effectively than novices"

View Source

Location PART 1 - TONS OF PUNKS, ONE BIG JERK CHAPTER 2: NO MOAT IN BLOAT No Magical Wand

Source title EXPERTISE IN DEBUGGING COMPUTER PROGRAMS

Source authors Iris Vessey

Source year 1984

Confidence high

Importance mid

Format Online paper / PDF

"Debugging struggles can cause frustration and stress and can influence whether students remain in computer science"

View Source

Location PART 1 - TONS OF PUNKS, ONE BIG JERK CHAPTER 2: NO MOAT IN BLOAT No Magical Wand

Source title Decoding Debugging Instruction: A Systematic Literature Review of Debugging Interventions

Source authors Stephanie Yang; Miles Baird; Eleanor O’Rourke; Karen Brennan; Bertrand Schneider

Source year 2024

Confidence high

Importance high

Format Web Page

"DVLA’s early-2000s modernization ran out of energy and money before completion, leaving old and new architectures operating together"

View Source

Location PART 1 - TONS OF PUNKS, ONE BIG JERK CHAPTER 2: NO MOAT IN BLOAT Humans Dig Fresh Quests

Source title Why some DVLA digital services don't work at night

Source authors Dafydd Vaughan

Source year 2025

Confidence high

Importance high

Format Video / YouTube Embed

"Michael Paulson rewrote Netflix Falcor request code and ended up reproducing the original almost line for line after encountering its edge cases"

Location PART 1 - TONS OF PUNKS, ONE BIG JERK CHAPTER 2: NO MOAT IN BLOAT Humans Dig Fresh Quests

Source title ThePrimeagen: Programming, AI, ADHD, Productivity, Addiction, and God | Lex Fridman Podcast #461

Source authors Lex Fridman

Source year 2025

Confidence high

Importance high

Format Book / Offline paper

"Steven Sinofsky described carrying old Windows components alongside new ones as a longstanding Microsoft pattern and contrasted it with Apple"

View Source

Location PART 1 - TONS OF PUNKS, ONE BIG JERK CHAPTER 2: NO MOAT IN BLOAT Humans Dig Fresh Quests

Source title Hardcore Software - Inside the Rise and Fall of the PC Revolution

Source authors Steven Sinofsky

Source year 2024

Confidence high

Importance mid

Format Online paper / PDF

"Technical debt and insufficient documentation were the two leading reported sources of developer time loss"

View Source

Location PART 1 - TONS OF PUNKS, ONE BIG JERK CHAPTER 2: NO MOAT IN BLOAT Humans Dig Fresh Quests

Source title State of developer experience report 2024

Source authors Atlassian

Source year 2024

Confidence high

Importance high