PHPBenelux Conference 2019
25 - 26 Jan 2019 at Ter Elst

It's a very interesting but also a very complicated subject and I couldn't quite follow it.

best perspective I heard about the subject in a long while.

Great seeing someone speak with so much enthusiasm about a subject that's frankly a bit stuffy. Also great to actually learn something new even if I already forgot most of it.

Great to learn the hidden details of the language you work with.

Thanks Bert and Sietze for your feedbacks.

@Sietze: Indeed, moreover, IDEs mostly show possible issues in the current/opened file while Phan will analyze the whole project. IDEs aren't that good for finding unused code (except for protected/private methods) and all of them *try* to understand PHP's syntax without using PHP, which always lead to some inconsistencies. IDEs knows the basic built-in functions, classes & methods, but not about the ones provided by less common extensions and will automatically lead to false-positives.
I also mentioned Continuous Integration, running Phan as part of your CI process is a must. PHPStorm isn't designed to be used in a head-less mode.

Cheers and thanks!

too bad that the big elephpant was not to win ;(

Thanks, everyone for feedback, and for attending the talk. I updated this talk with slides.

@Bart McLeod

> Unfortunately for me there was no new insight in the talk, I practice what you preach basically. This is reassuring, but of course I had hoped to learn some new things as well.


Wow, you are awesome. Probably you should also share your testing experience as a speaker. Maybe there is something I can learn from you about testing ;) Or maybe you could guide me what topics could be added / extended.

Great talk. Very informative but also entertaining. It got me inspired to read the book.
Also bonus points for having to answer questions from Marco. (He is always watching)

Very nice talk (texas joke still funny the 2nd time :D) Where you lost me for a moment is when you showed us the code snippet inside a tweet part. The code is hard to read (mostly due to the lack of proper names). While the code inside 1 or 2 tweets is cool I think it isn't right for the purpose of the talk. If those examples were more easy to read I think I would've followed that part better.
Thanks a lot for the great talk.

Very nice talk. Not only did you explain to us how to handle security on wide scale. You also taught us the basics of how a nuclear reactor works. Very well done. The nuclear reactor part was a great guiding story to the rest. It really fit in well. It also showed me things I usually ignored (for example threats from inside the company network).
Thanks for the great talk and insights.