Liked the subject and especially the part which emphasized the usage of appropriate tools that allow for reviewing as closely to the code as possible.
Agree with the commenter who pointed out that less text on the slides and more movement on stage would be a win - but I'm also aware that giving a talk is hard.
From the title alone I would have expected the content of the talk to be more focused on actual application architecture, but as Volker pragmatically pointed out in the closing keynote, "it depends" would be the default answer anyway.
In my experience, using diagrams has helped a lot, but I've not yet used them in an agile context.
I fully agree, though, that more time should be spent on actually designing the architecture of an application and especially discussing it.
As commented, I've found it it very hard not (!) to refactor existing code at times where a tight schedule was used as an argument to forbid it by management.
I fully agree with Robert C. Martin, Martin Fowler, and the like, who suggest to refactor along the way while you're reading code, given you intend to work on it.
However, you can easily refactor yourself into a corner where no one is willing to review or merge your PR if the culture on a team / project doesn't allow for it.
Probably time to move on, then.
A talk that went far under the hood of what's under the hood, dealing with what most PHP developers probably never have to deal with - but nonetheless leaves us with a number of suggestions of how to write better code.
Entertaining as always, Anthony is a great and very knowledgeable speaker.
Clearly, I should have studied computer science instead of dropping out of business school!
Great tutorial! I especially liked the suggestions for refactoring an existing application with has a lot of client-side code with jQuery to something more modular, leveraging Backbone and Underscore, as I've travelled down that path myself and found it extremely useful and light-weight libraries to understand. Also, great examples of how important it is for PHP developers to get comfortable with shifting from server-side only development to single-page applications, with thick clients talking to APIs.
I'm definitely going to give Flysystem a try, and moreover, suggest it to other developers on my team who didn't make it to the conference, but need to wrestle with AWS uploads.
Quick, sweet and convincing talk!
Wrote my first Go program during the talk. It outputs "Hi!" on the console, and its compiled version is only 1.8MB!!!!11
Benjamin clearly knows what he's talking about, I found it a very interesting, informative talk.
Chris' talk was a great reminder that there's a lot more to just shipping an application in a timely fashion and made me want to look at the OWASP guides again. Also, Chris has a very pleasant voice, so I believe he could talk about anything and still make for a very, very good presentation.
Thorough overview of static code analyzers covering different aspects of a code base, whether run from the command line or as SAAS.
Not entirely sure if I missed it, or because it's just that there are too many SAAS for that, but there are also
- Code Climate
- Scrutinizer CI
I already had a feeling that moving a large legacy code base from PHP5 to PHP7 is quite a challenging task, but thanks to this very detailed talk, I am now convinced that - while necessary - the challenge should not be underestimated.
Already seeing a lot of problems ahead of us, hehe!