Roy van Rijn explains what mutation testing is and how it works, comparing several Java frameworks (PIT, Jester, Jumble) that enable automatic mutation testing in a continuous build.
Jerry Yoakum discusses how code profiling tools and techniques can be used to evaluate code for constructions and errors that are likely to cause problems, highlight places in need of refactoring.
Austin Bingham answers questions on reviews: how long should they be, what should be reviewed, how do reviews account for an increase in quality and ROI?
John Housego describes how W. L. Gore & Associates manages to maintain a global corporation without hierarchies, that keeps the bureaucracy as small as possible.
Nathan Peterson introduces Behavior Driven Development, showcasing its adoption by his team along with successes and failures using it.
Keran McKenzie takes a look at internationally successful developer programs looking at what developers love and hate, to show how to create, deliver and maintain an API community.
Linda Rising talks about organisational change myths and patterns for introducing new ideas. She provides some useful tips for helping you start to grow, step by step, any innovation.
Melissa Greene explores the pitfalls of management.
Alison Lloyd examines some less-than-stellar occurrences in non-software fields, drawing out some ideas that she hopes will make software development a little less painful.
Giannakakis and Dalkitsis present how Shazam releases faster, more predictably and with more features by using BDD and automation testing, without slowing down or hindering the development process.
Big Design Upfront was considered so evil in the early days of Agile that it acquired its own acronym. It’s time we relearned that great products start with asking the right questions.
Dan North describes a model for thinking about the age of code and argues for replaceability as a first class concern, ending up with something that looks a lot like microservices.