Organized for Antiquity — Software Engineering’s Fundamental FlawWhy We’re Organized for a Distant Past and How to Organize for Modernity InsteadMar 27A response icon9Mar 27A response icon9
The Bureaucratization of AgileWhy Bureaucratic Software Environments Aren’t AgileFeb 12, 2024A response icon5Feb 12, 2024A response icon5
Utilization Considered HarmfulWhy It’s Costly Keeping Everyone Busy in Software OrganizationsNov 6, 2023A response icon5Nov 6, 2023A response icon5
The Siren Song of Software PlanningWhy Experiments Work Better Than PlansSep 6, 2023A response icon1Sep 6, 2023A response icon1
Collaborative Ignorance in Software EngineeringWhy We Believe What We Think Our Group BelievesNov 3, 2022Nov 3, 2022
Paying Someone to do Our Homework: The Risk of Mediocrity with Agile FrameworksWhy Adopting Agile Frameworks is not a Risk-Free EndeavorOct 9, 2022Oct 9, 2022
It’s What We Know that Just Ain’t So: Epistemic Failure in Software EngineeringA Review of Our Industry’s Knowledge Failures and Methods to Overcome ThemMar 1, 2021Mar 1, 2021
Accepting Uncertainty: The Problem of Predictions in Software EngineeringWhy our predictions continually fail and how to improve our results with learning-based approachesJun 1, 2020Jun 1, 2020
