This was a great topic for me and my team. I am somewhat new to my company and have inherited a mass of legacy code. If we could go thru these steps, I think it would make huge improvement for future dev efforts and maintenance. We have much to discuss on this.
I'm still new to PHP, but I felt this was a well-spoken coverage of the trends in TDD. I have much to still learn in this space. I need to share the slides with my colleague who was in another session, so we can discuss. I also need to read those books.
Very well done! I have been wanting to go more towards the model of an api feeding an angular or angular like system and this helped me see a good way of structuring that API. I agree with other comments that you probably don't need to show the use of multiple frameworks. Just a short explanation that the code is basically the same would probably do the job in far less time.
This was a very good review of the history of PHP and how it has grown from a simple scripting language to an entire community of developers that are helping each other to build good reusable code so they can build their software solutions faster and cleaner. Jonathan does an excellent job at explaining how you can use composer to build a solution to the system you are trying to build in minimal time by leveraging the work of other developers which they want you to use as well as how you can help contribute to that community.
Ben was able to show good knowledge of the source material and gave a very good intro into how Laravel works. Unfortunately, I missed the very beginning of the presentation so I was a little lost but the part I did see was helpful in allowing me to hear the terminology of Laravel and get me started. I will definitely be looking into it further and probably Lumen as well since we are looking at building an API.
He makes a very good case of why we shouldn't be trying to rebuild all the time. I would have liked to see a little more inspection of the reason why rebuilding is a bad idea though. It seemed like the main reason presented was because it had failed with a bunch of other products. The problem I see with just giving examples of when it failed is that it wouldn't too hard to find examples where a rebuild succeeded.
I have been trying to get a better handle on Unit testing and mocking for some time now and even though Ben's presentation was on a specific tool, it also helped me greatly in understanding the general process. I had the opportunity to talk with Ben at lunch after the presentation which helped even more with finding ways that I can start to implement unit testing even in my legacy application.
Very well presented! I never even thought to ask my employer if they offer mental health benefits. I know my current employer does not since they don't offer any benefits but in the future where it is possible, I will be sure to look into and encourage it.
Very well presented. I was never disappointed by one of Davey's presentations. Very knowledgeable on the subject matter and really got me excited about the possibilities that HTTP/2 will bring to the table.
Margaret does a great job at introducing Doctrine and describing the benefits of using it. I was looking for something to give me an idea of how Doctrine works and that is exactly what I got. The only feedback I would give would be to slow down a little. Maybe the speed was intentional to try to get as much info in as possible but it was a little excessive to me. I would also say that it would be good to get more familiar with the different ways that Doctrine can be used so you are better prepared when people ask about ways to do things that you haven't tried to do. Very good presentation though.