Being responsible for quality starts with the code. This is challenging since code quality is a broad and ill-defined concept. Not only is "good code" contextual; the invisible interactions between developers and code are just as important as any properties of the code itself. To get the largest bang for the buck we would need strategies that let us prioritize delivery risks based on contextual data from how the system evolves. Where do you find such strategies if not within the field of criminal psychology?
This session reveals the wealth of information that's stored in our version-control systems. You learn to predict bugs, detect powerful social patterns in how developers collaborate and explore visualization techniques for prioritizing improvements to the areas of the system that are likely to need it the most. Along the way you also see how you mitigate off-boarding risks in your codebase, learn the pitfalls of teamwork, and much more. The session targets testers, technical leaders, and developers. All examples are from real-world codebases like Android, the Linux Kernel, Roslyn, and applies no matter what technologies you use. As a bonus, you'll get an introduction to modern offender profiling and its powerful counterparts in the software world.