To improve your code base, you run an audit. Now, with so many diagnostics, the situation appears to be overwhelming. If you have a mere million lines of code, it may display thousands of errors, in various orders. And with that, the market leaves no time to reduce technical debt before the next feature: we’ll do it when pressure gets lighter, right? WRONG!

Code quality starts with a daily review. Learn how to navigate in the results of code audits that actually find more issues than you want. During this workshop, we’ll check PHP classic traps, architecture errors, security vulnerabilities and logical bugs. We’ll see how to detect those bugs, how they happen, and how to prepare a fix (or not). By the end, you’ll be able to set up your own coding reference, the one that reflect your style of coding in your projects.


Comments are closed.

Dana Luther at 16:09 on 7 Feb 2019

This tutorial was excellent. I wish we had time to actually try to generate the reports, but it gave me lots of homework to do ;)

Nate Bockoven at 10:49 on 8 Feb 2019

Gave me a better idea and concepts of things to look for, and a tool to find how to improve my code.

Awesome idea, good energy, not too well executed.

Parth K at 15:44 on 8 Feb 2019

Expected a little different code review session. As a beginner to the language, it was sometimes going over the head. Having said that I learned a lot.

Adrian Burden at 10:08 on 9 Feb 2019

I liked the introduction to the tools that I can use to analyze and audit my code base.

Brad Reed at 11:44 on 9 Feb 2019

I was introduced to some great new tools and found myself challenged by the exercise. I would have loved for this to have been an ongoing course with the chance to review multiple code bases.

Was an interesting interactive experience. I was a bit late, when I arrived Damien asked what I was personally looking for in this talk, and he pointed me where I can exactly find it.