I really enjoyed the snowmobile parallel at the beginning, and the talk gives a great overview of not only why metrics are important but specific tools that we can use to help put numbers to the broad idea of code quality (e.g. static code analysis, coverage, etc.). Better yet, I picked up a few new ones that I haven't worked with (PHPMD, PhpMetrics, pheromone/phpcs-security-audit)
I think the talk would benefit from a bit more "the numbers help tell a story, but it's not everything" (e.g. you could have 100% code coverage, but if the tests are only covering the happy paths there's limited value). Knowing that talks like this will tend to attract leadership types at the conference, it's probably important to include this disclosure ;)
Solid overview of current tooling around checking the health of your project. Included style tools, guardrails, and static analysis
It built quite nicely onto the PHP value object talk
Great foundational material for thinking about tests, their value and solid examples of what makes the test code itself useful to a developer.
Great points to quantify the value of a test. Using Battlesnake to demonstrate was a perfect way to wrap up.
As someone who eats, sleeps, and breathes automated testing I *loved* Tim's reasonable approach (e.g. "here are the 'rules', but here's where you get *value*".
I was a little concerned when it turned into a Battlesnake tutorial in the back-half, but the examples were extremely relevant and tied back nicely to the first half.
Nice real world examples.
Great talk with actionable examples. Great speaker.
5 stars for the jokes.
I think I've seen this talk twice before I till get something out if it, thank you