Software Architektur im Stream

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.

Links

• Laurent’s Book “The Leprechauns of Software Development”
• Derek M. Jones: Evidence-based Software Engineering: based on the publicly available data
• Hillel’s talk “What We Know We Don’t Know”
• Hillel’s consulting

Additional Links

• How students learn
  • Reframing the Liskov substitution principle through the lens of testing
  • Executable Examples for Programming Problem Comprehension
• 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-word Identifier Names
  • Recurring opinions or productive improvements—what agile teams actually discuss in retrospectives
  • Andy Oram, Greg Wilson: Making Software
• Code Reviews
  • Expectations, Outcomes, and Challenges Of Modern Code Review
  • Characteristics of Useful Code Reviews: An Empirical Study at Microsoft
• Criticism of existing reasearch
  • Hillel about “This is How Science Happens” - criticism of a code minin paper
  • Hillel’s newsletter: I **ing hate Science
• Hillel about “Are We Really Engineers?”