Ski PHP Conference 2014
17 - 18 Jan 2014
at Salt Lake Community College
Talk comments
Great content, thorough and well organized, plus an entertaining and engaging style. Well done.
Awesome talk. Loved learning about Grunt and seeing all the different ways I could use it in my projects. Super useful information and I'll be using Grunt and Bower in my future projects thanks to this talk.
Lots of good post-mortem information.
Seemed very WordPress-specific, though the talk synopsis doesn't mention that focus.
Some of the slides were really difficult to read because the text was so small and there was so much information on there. Specifically the resources page, which you went through lots of the points individually. Perhaps split those out to different slides when you're talking about them?
Great presentation overall. Good use of examples and references for further learning. Enjoyed discussion at the end especially.
Good information, but short.
It would be awesome to flesh out some of the attacks with some real life examples.
Such a great talk. I hope the dialog can continue in society, mental illness isn't anything to be ashamed of.
Great talk! Loved the way the presenter walked through each example step by step.
I found the talk very informative. I learned a lot about effective use of SQL and related technologies. The speaker gave strong opinions and advocated certain approaches, but backed them up with detailed reasoning and examples.
His perspective on large scale systems seems consistent with what I've learned in my own systems background from Stanford graduate studies and work at places like Amazon.com.
Excellent introduction into DI. It is a buzzword in our community and almost seems necessary for the businesses who plan to grow their digital products. I would love to see more real-world application and more information on ROI.
Good talk on how to recover from a wordpress site getting hacked. I think the suggestion to control the site through git or mercurial provides a very good way to determine if the site has been hacked and quickly recover (or more quickly anyway). Beth's comment that the repo should be read-only is good as well but if the user is keeping track of the hash that the code should be on, it should be simple enough to get back to that point and remove any compromised code that may have been injected.