Longhorn PHP Conference 2022
3 - 5 Nov 2022
at Holiday Inn Austin Midtown
Talk comments
Great talk, good humor, great examples and relatable stories. Well done!
Excellent content and delivery. Please can you share your PPT here OR those nice quotes.
Really great talk, great content & delivery.
Good pacing, delivery, and content!
Really lovely and very helpful, especially for a developer who is relatively new (2 years in) to their career in development. This was Chris' last talk on testing, but I can't wait to see what he teaches about next. he's a great teacher.
Very interesting talk, really enjoyed it. Looking at the interactions I think that a lot of this would be useful implementing something similar in Teams or Discord. Excited to see the implementations though php and am excited to try and implement my own app.
Feedback Points:
1.) Without a locally installed php there was little I could do, with the socket work this could be running in a docker container to allow for more globally runnable code. You could even store the different demos on different branches.
2.) It would be helpful to have the slides available to view and follow along with and to copy things from.
Really lovely and helpful. Being able to follow along in the code was super helpful in terms of understanding how things work. I'll probably go over it again at home to make sure I know things, but this talk really made me feel like I was getting things started on the right foot.
Really enjoyed the presentation and tutorials to get a visual working sample of the services. This helped me to see how the systems talked to one another, through registration to authentication to execution. I was excited to get to see this and was not disappointed. Thank you for all the information!
A few feedback points:
1.) Several of your information slides (title slides) have very low contrast and are not able to be read easily on the screen.
2.) There is a lot of copy & paste in very specific places in very specific files. It might be help full to use git branches to have "save" places ... like lession1_start, lession1_final ... etc so even if they completely messed it up, they can checkout a clean working tested version of the code to allow them to run it. (this also helps you cause you will always be able to jump to the right version of the code for demonstration purposes :-) )
So helpful and well explained. I really appreciated the insight into a topic that I am actively working on growing into.