Thanks for the talk! This gave me a lot to think about and how I can bring some of these concepts back to my team and organization.
Thank you for the talk. I still feel like there are gaps in my understanding of how I could and should use Verbs but I think I just need to try it out.
Thank you for the talk. I wish there was a way to force API designers to follow your rules because I'm sick of 200 status codes that return an "error" message.
Thank you for the talk! I got a little confused with some of the examples but I think that was a "me" problem.
Prism looks super cool. I wish I knew more about it before this tutorial as I felt I could.not keep up and eventually had to abandon trying. It is clear TJ is really smart and knows the domain inside and out. Unfortunately as a tutorial session I expected a much more deliberate Hands on approach that helped me actually use the tool and get comfortable with it.
Thay said, I am enthusiastic about exploring Prism but it seems I will have to do some exploration of the docs.and other resources.
This talk has *a lot* of information, and Damien obviously understands the topic deeply. That being said, this talk is very academic, something I'd expect in a university course. Several suggestions (like "don't use void") is from a type system point of view, but at least a few people in the audience were like "wait, then what should I use when I don't need to return things?"
The examples were rather abstract (e.g. class A, class B, etc.) which made it difficult to follow along with the more complex examples, but there was enough context clues that I didn't get totally lost.
One suggestion I might offer is to explain that, for example, "M 24" refers to Method #24; it's a reasonable abbreviation, but not something I've seen before.
I wanted to like this talk but I am afraid it was quite light on detail or examples. It also finished quite early, so I think there was plenty of room to add more substance.
I really liked this talk. It was very approachable and informative. It gave me some things to think about and take away. I haven't found great tooling for secrets management in php but maybe I just need to look harder.
Thought provoking talk. Reviewing code from the type perspective (ignoring function names, etc) is presented as a mindful conversation.
Thanks for the tutorial. It gave me a good overview of how I can write my own rectors which I need to use to rewrite some of our legacy code into more current Laravel standards.