Decouple your framework now, thank me later

Great talk one of the best of the weekend I think. Very thought provoking

Talk started at 11:10 and we were at questions by 11:25. Also slides were unclear and text way too small. The only advice given was "use interfaces"

Very short and unprepared. Also would have expected a mention of Laravel—one of the tightest-coupled framework—in the talk and maybe best practices or tips on how to write code decoupled from that framework.

Food for thought, you use a framework, but your business logic shouldn't. Decoupling the two is the topic of Michelangelo van Dam's talk, and he covers it quite well.

Despite being a topic that I'm very keen on, I was disappointed by this talk. The delivery was a little dry, and for a full conference talk lasted only 15 minutes + questions. Unfortunately the code heavy part of the talk was un-readable, and there was an apology for the fact some of the code/talk was being worked on at 4am. I think this would have been well suited to an un-con talk, but for a conference talk, more preparation and content would be needed.

This talk was on an important topic but was too short it felt like it never really got started. The slides were impossible to read making it that much harder to follow. No real advise or solutions talked about apart from using interfaces more content is needed for this to be more useful.

Felt very rushed and the demo code slides were illegible so unfortunately I didn't learn much at the talk. Having access to the code though will ensure I can digest it better later. Talk started well but unfortunately, due to the clarity of the slides, fell down from the middle.

It's always good to hear about better ways to decouple code and business logic from other areas of your code, but unfortunately this talk consisted pretty much of "Interfaces are good, use them" and that was it really. I was really surprised that we were at the end of the talk after 15 minutes - I would have liked to see some more real-world use cases and examples of how you can take highly-coupled code and the approaches you'd take to gradually decouple it. Feels more like a lightning talk at the moment.

I was looking forward to this talk perhaps the most of any, but was rather disappointed. It was extremely short and there wasn't much in the way of advice other than to use interfaces between your business logic and any framework you might hook up to - something which is just the basics of decoupling in the first place. I would have liked more insight into problems encountered, perhaps some downsides of doing it, particular 'problem' frameworks to apply this technique to or some examples of instances where it might not be appropriate perhaps.

I was interested to hear what others were doing to keep the domain / BI clean, but sadly the talk was very short with unclear slides that did not go into enough examples. If would be much better to tackle this topic by typical area e.g.: authentication, models and entities, validation etc. These areas tend to get the highest coupling (Eloquent models, SF validation, annotations etc) and would definitely benefit from a deeper dive.

I liked what was there but it was about 1/3 of the content I was expecting to get