wiki.accu.org

This page is read only. You can view the source, but not change it. Ask your administrator if you think this is wrong.


Back to [[conference:committee:proposals-2013]]\\
\\
**Title**: Code as a crime scene\\
**Proposer**: [[2013:adam_petersen]]\\
**Type**: Tutorial\\
**Duration**: 45 minutes\\
**Description**: 
Human intuition is unequaled when it comes to assessing the quality of a design. Intuition, however, is not without problems. It's prone to social and cognitive biases that are hard to avoid. Human expertise also suffers from a lack of scalability. As such, intuition rarely scales to encompass large software systems and we need a way to guide our expertise.\\
We need strategies to identify design issues, a way to find potential suspects indicative of code smells, team productivity bottlenecks, and complexity. Where do you find such strategies if not within the field of criminal psychology? Inspired by modern offender profiling methods, we'll develop a metaphor for identifying weak spots in our code. Just like we want to hunt down offenders in the real world, we need to find and correct offending code in our own designs. \\
The session will look into test automation, software metrics and findings from different fields of psychology.\\
\\
Ewan: MAYBE. Looks in the same ballpark as "An Exploration of the Phenomenology of Software Development" - room for only one of them?\\
Roger: I agree\\
Asti: sounds interesting \\