Writing Effective PHP

unfortunately missed the first 10 minutes, but what I saw was solid.

A very good talk with lots of useful insights.

Very useful insights.

Great talk, very informative and some great packages that I'll be sure to use in the future

Helpful and new ideas introduced & potentially very useful tools

Great talk. Some of the scenarios were too idealistic and we talked about it during break, but overall good talk.

Very nice and structured talk.

Thanks Nuno, this was a great talk that gave me lots of things to consider in writing my code. I particularly liked the analogy with defensive driving!

Very useful, great insights, excellent delivery!

Really interesting talk!

Solid opinionated take on writing code with some definite food for thought going forward!

opinionated but great otherwise

Seen this talk now the third time and it even gets better every time. Nuno is a great speaker and has some brilliant tips for writing better PHP. I really enjoyed his presentation and I can take great insights with me. There is nothing I can complain about.

A great way to start the conference. Immediately provided valuable lessons that anyone could go away and work with.

I was aware of most of the topics and opinions raised but it definitely helped me understand why they are important especially when working in a team

Good talk and picked up some useful packages

Very interesting, inspiring talk and very well presented.

A really good talk, well presented and good content in the slides from what I remember.

My only issue as such was first half and last half didn't necessarily gel that well, it felt like you talked about defensive programming really well, then you talked about your tools for doing an analysis but never really tied it back to how your tools would change things for a dev. Might be worth while having an example project where you ran the tools showing what you detected and give the audience something actionable for themselves. For example, in an example project with some glaring static problems, show what came back in the results and then quickly resolve and show the tool. Maybe provide a workflow for how you fit doing that static analysis into your development because it's something a lot of devs don't use still in my opinion.

I say this as someone who has installed Larastan and Insights before the talk but still haven't got to grips with it and found it generating a lot of noise and not knowing from the docs how to make it apart of my processes.

Thank you Nuno for your talk. I am new in the php and Laravel community and did not know PHP STAN and PHP INSIGHT. Every developper should know them.