All developers know that bugs are bad and finding them can be difficult. The good news is that tools to help us find and prevent them are becoming more powerful. Modern static analysis tools (like Psalm, Phan and PHPStan) are far more advanced than their predecessors. They can find a whole range of bugs whilst keeping the false positive rate low. This talk introduces more advanced static analysis. It will show the kinds of bugs that the more advanced static analysis tools can find. We’ll then look at how they can be added to your current development work flow. Finally, we’ll look at how we can write our code in a way to get the most out of static analysis.


Comments are closed.

Lucia Velasco at 21:19 on 27 Sep 2018

Good topic, I enjoyed pinning down "what is a bug", you had some very instructive examples.
I would have liked to unpack the statement "a static analysis tool should understand your vendor directory".
I found that this was a great talk for PHP, coming from a TypeScript background some of the discussion around generics, packages and typehinting was a bit exhaustive.
I liked the interactive/audience participation prompts!
It was interesting learning how SARB works - I love learning about behind-the-scenes of handy features!
You're good at paraphrasing from the slide, which keeps me engaged.

Rhys Laval at 21:22 on 27 Sep 2018

Good talk and great examples for what could be seen as slightly a rather dry subject.

Mike Oram at 21:29 on 27 Sep 2018

Great talk, I like the intro about reducing bug costs and the idea of realtime static analysis in PHPStorm. I'd like to see some info about using PHPStorm autofixing some of the issues. It can do that on mass which is super helpful! And fairly easy to demo. Pace of delivery and difficulty was well pitched and promoted good conversations.

Great talk, I really liked the story you told of your journey with real and relatable examples of most points you made. It was encouraging and accessible to all levels of developers. Perhaps some of the sections of walking through code were a little longer than necessary, but in general a brilliant talk. Thank you