We all have some ideas about what works in software engineering and what doesn’t. But without real evidence and data that is just an opinion. Empirical software engineering tries to answer the question of what can be proven to work in software development. In this episode, Hillel Wayne and Laurent Bossavit will talk about what we know about software development, what we don’t know - and the myths about it i.e. what we think we know but really don’t.
Laurent’s Book “The Leprechauns of SoftwareDevelopment”
Derek M. Jones: Evidence-based Software Engineering: based on thepublicly available data
Hillel’s talk “What We Know We Don’tKnow”
Hillel’s consulting
How students learn
Reframing the Liskov substitution principle through the lens oftesting
Executable Examples for Programming ProblemComprehension
What we know
It Will Never Work in Theory: Short summaries of recent results in empirical software engineering research
Fixing Faults in C and Java Source Code: Abbreviated vs. Full-wordIdentifier
Names
Recurring opinions or productive improvements—what agile teamsactually discuss in
retrospectives
Andy Oram, Greg Wilson: Making Software
Code Reviews
Expectations, Outcomes, and Challenges Of Modern CodeReview
Characteristics of Useful Code Reviews: An Empirical Study atMicrosoft
Criticism of existing reasearch
Hillel about “This is How Science Happens” - criticism of a codeminin
paper
Hillel’s newsletter: I **ing hate Science
Hillel about “Are We ReallyEngineers?”