Longhorn PHP Conference 2019
2 - 4 May 2019
at Commons Learning Center
Talk comments
I loved this talk! I recently "went bare" in a small side project and I second guessed myself every step of the way. This talk and Sammy's amazing energy and information validated the decisions that I had made, as well as provided inspiration for new things I'd like to do.
I enjoyed Sammy's breakdown of "when" to "go bare" (ie: greenfield vs. legacy code). Seeing some ways to introduce modern code, packages, and bare PHP into a legacy framework application was a huge plus and selling point.
Sammy had great energy. The way in which he structured the presentation, the problem and solutions, and the way he walked through each step as the next logical step, made it really easy to follow and relate to.
Good informative talk. Would have liked a little more detail about getting started with PHPstan. Great examples for once you are setup though.
Jen was definitely not a "dumpster fire." Great introduction to bootstrapping accessibility reporting using Pa11y.
Slides: https://tehfedaykin.github.io/pa11yBFF/
Great presentation on what seems to be a great tool. Speaker was lively, but sometimes spoke a bit fast.
Awesome talk, energetic speaker. I have used a GUI version of Pa11y before and seeing the JS features of Pa11y makes me want to use it instead!
Great talk and intro to Pa11y, good examples, and lively presenter.
Great talk about testing and application structure but I was expecting an intro into an automated CI strategy using PHPstan.
Great examples irl and code.
I'm a big advocate of going bare. It's great to get another perspective on going bare, and hear from someone who's a little more like "going bare is good, but also frameworks are good". And it's great to see other ways of doing things in the examples of how the bare application is bootstrapped and set up.
Great talk with some good examples of bad and good code. Ondřej does a great job of explaining why some code is bad. I am taking back some things I need to change in my code and how to better use a static anylyzer in my workflow.