PHP Tek 2026
19 - 21 May 2026
at Sheraton O'Hare Suites
Talk comments
Another fantastic PHPStan talk from "Static Analysis Dave". This talk would have saved me a couple hours of troubleshooting just a couple weeks ago, and I only made it through by looking for some of Dave's other works.
Lots of good technical details about setting up and using MCP servers, great talk Chris!
Great explanations and examples of how to exploit a real vulnerability and how they can be exploited.
You SHOULD see this talk, while you COULD do code review without it, there are plenty of MUST have insights Andy delivers that are relevant to what developers are working with right now.
But seriously, it's a great talk and I know that his insight has been practically tested and validated and shown to be incredibly valuable. It's not a 'well, it would be nice if we did it this way' theory, it's 'this is what I've found to be successful working on a high performing team'.
Excellent talk! It was really interesting and informative to not just learn about what the exploits were, but _how_ they actually worked. Good examples and well presented.
Good pace, humor, and topic selection. Solid refresher even for advanced developers.
Another fantastic talk from Mr. Andy Snell. I really appreciated that he took the time to break down must/should/could/etc. for reviews, as well as addressing the technical aspects *and* social contract.
It was a little AI-heavy for my taste, but that's not exclusive to this talk (it's an industry-wide issue).
Really great insights, presented clearly. It's a shame that venue issues prevent Nia from presenting on the big stage in the ballroom.
MUST: The content is excellent — lots of great advice. Keep all of it.
COULD: Add a proper introduction of who you are before or towards the start of the talk.
SHOULD: You jumped right into the talk. Since you were the first speaker of the day: it would have been good to check that people could hear you.
COULD: Give a general overview of the talk before jumping in. That said, I liked your opening — perhaps keep it, then add a quick overview after.
COULD: Slow down. You spoke a little too fast, especially at the beginning, though you did ease into a better pace as the talk went on.