Useful talk for covering GoF design patterns in PHP. I was hoping to see more examples of how these design patterns might be applied to refactor real-world technical debt.
Found this to be surprisingly helpful, but, as a key take away, would be good if a directory there were available on the net of the code examples of each design pattern. Would be great!! Thanks.
Despite the obvious knowledge of the presenter the content didn't really reflect the title. The talk was more about 'preventing technical debt from being incurred' than 'reducing technical debt' that already exists. It would be helpful if the talk really followed tutorial format with some real life examples and code refactoring. As is it fits regular presentation session more than it does tutorials.
Talk was fine. Ran short, but there was a dearth of audience interaction. I think the bigger issue was that it felt like we just rushed through a lot of design patterns, and didn't actually dig into how to use them.
There were many code examples, but a tutorial would have been probably better. The examples were hard to see - perhaps black text on a white background would have been better...
One big thing out of the gate - this was labeled as a 3 hour tutorial, yet only lasted a bit over an hour. From the content being presented, this wasn't just a rush or lack of audience participation. I feel like this was an hour talk. There just didn't feel like enough content nor things to do to ever come near filling the entire slot.
I also feel like the talk was misrepresented in it's content. This was, at it's heart, a design pattern talk. From that perspective it did it's job well - it introduced the most common design patterns and how they work. The talk did not do what was on the tin, which was teach how to use them to reduce technical debt, nor how using them future-proofs your code.
My suggestion would be to just make this a 1 hour design pattern talk, and it will be a much better representation of the content.
Comments
Comments are closed.
I enjoyed the talk. It's always great to get another perspective on a topic of great interest to me.
Useful talk for covering GoF design patterns in PHP. I was hoping to see more examples of how these design patterns might be applied to refactor real-world technical debt.
Found this to be surprisingly helpful, but, as a key take away, would be good if a directory there were available on the net of the code examples of each design pattern. Would be great!! Thanks.
This talk was full of very useful knowledge. Speaker needs to work on organizing the information in a way that keeps people engaged.
Despite the obvious knowledge of the presenter the content didn't really reflect the title. The talk was more about 'preventing technical debt from being incurred' than 'reducing technical debt' that already exists. It would be helpful if the talk really followed tutorial format with some real life examples and code refactoring. As is it fits regular presentation session more than it does tutorials.
Talk was fine. Ran short, but there was a dearth of audience interaction. I think the bigger issue was that it felt like we just rushed through a lot of design patterns, and didn't actually dig into how to use them.
There were many code examples, but a tutorial would have been probably better. The examples were hard to see - perhaps black text on a white background would have been better...
All around, a fine talk - 3.5 stars.
Also expected more examples. In general all main patters were covered.
One big thing out of the gate - this was labeled as a 3 hour tutorial, yet only lasted a bit over an hour. From the content being presented, this wasn't just a rush or lack of audience participation. I feel like this was an hour talk. There just didn't feel like enough content nor things to do to ever come near filling the entire slot.
I also feel like the talk was misrepresented in it's content. This was, at it's heart, a design pattern talk. From that perspective it did it's job well - it introduced the most common design patterns and how they work. The talk did not do what was on the tin, which was teach how to use them to reduce technical debt, nor how using them future-proofs your code.
My suggestion would be to just make this a 1 hour design pattern talk, and it will be a much better representation of the content.