I am really pleased with how Jordi delivered the scopes of the brilliant saviour of dependency management for PHP "Composer". Thanks for sharing with us!
This was an excellent topic, delivered well.
This was interesting topic, although it went in a rush giving sort of a quick overview on which design patterns been in use with Laravel. For those who are new to design patterns may have expected a little bit more. Thanks Phil, you did well.
Nice topic. A bit rushed. I knew the childish head design boom, but what was the name of the "real" book again?
Great talk, nuff said.
Talk was good. Would've ideally liked a talk on a different (more technical maybe) topic from the *creator* of Laravel, but ignoring my personal wishes, the talk went really well and there's nothing I can say against it.
I think Kapil's ideas are very interesting, writing a complex application will end up making a complex architecture, so hiding the 'ugly' code in the service-provider layer to provide yourself with the 'eloquent' code for normal stuff sounds pretty sensible.
Kapil is obviously a very talented programmer, but as Kirk said, I think we really needed more time with the codebase than the presentation afforded. I feel some of the low marks here may have come from people who didn't get it. I have a feeling that most people writing the kind of application Kapil appears to be doing in this talk would end up with much less maintainable and uglier code. I'm really interested to see where this goes and would certainly like to follow along with development.
My expectation based on the topic and what was delivered got me into some level of confusions, although this could have been a gap between what was communicated. I did expect this topic to cover more on the complexity of an application with real world use cases. The topic says "Engineering complex application" which certainly feels like it should have been better to if Kapil could show the stages of a complex application development which involves complex situations and dealing with such situations in a programming context, rather than just a structure. Something more like dividing the complexity to simple parts to solve the problems, or in other words "divide and conquer". I am trying to be honest here. Thanks.
I'll never outsource to India
ill use symfony from now on