A bit too sketchy for my taste.
However presenter pointed out several important things. And separate thanks for mentioning that you're refactoring not because you have spare time to waste, but when you actually want to change the code and not satisfied with what you currently have (I believe this should be mentioned in every refactoring-related talks).
P.S. If this talk was offered as 3 hour hands-on tutorial, I'd definitely make more out of it (and Benjamin will finally have enough time to show everything he planned to).
I don't see how client side messaging can be not security related. It is the cornerstone issue for non-native clients (at least at this point of time). So, I believe this talk is a nice overview of different alternatives available.
The best talk! Well balanced, just enough theory so that you can grasp the concepts even if you are seeing them for the first time.
Amazing introduction to Halting Problem, definitely presented better than in most CS books :)
Very good talk.
I've attended it after attending the PhpSpec one, so got a more complete understanding of a possible toolset (for communication, design, validation).
Plus, during conversation with Tobias, I had an opportunity to ask couple of questions regarding general workflow, which cleared up things even more.
So, now I plan to spend more time evaluating all three tools (phpspec, behat, mink). Which is a nice outcome of attending a conference talk, don't you think?
Thanks for your comments! They should make my future presentations better.
It seems, that the main problem is that everybody expected a more hands-on approach, while I never mentioned that this tutorial will be hands-on (you can re-check talk description, it is up there at this very page). Moreover, I specifically pointed out that setting up VMs is not strictly required, just if you want to try things as I talk about them (like trying to get authentication token etc).
So, while I haven't mentioned that this tutorial will be a hands-on experience, I believe it is a good idea to turn it into one. Therefore I will work in that direction, thank you!
Despite the low raring, I still believe that theoretical content was good and solid, so if it is only buffalo that made it into memories, then it should be my presentation skills, not the content :))
To anonymous (btw, why so?):
If you check the ansible roles (I have spent lots of time creating) https://github.com/farazdagi/rest-tickets/tree/master/roles you will see that there's yeoman role + common role that sets up necessary node.js files. Just uncomment "yeoman" here: https://github.com/farazdagi/rest-tickets/blob/master/site.appservers.yml Finally, there's a separate slide in my presentation when I mention tools necessary (and I talked about tools as well). Overall, I suggest you look into code provided - it has lots of value in it (and will definitely save you some time googling).