I enjoyed this talk very much. I am going to make a concerted effort to steal all the slides from the beginning of this presentation to try to convince my bosses we need to work on this ASAP for our site. Also, you may have convinced me to go to your design talk tomorrow.
I thought this talk was very good, particularly for people that aren't familiar with it. I will be using these concepts in my job, not necessarily to do things I haven't already been doing, but to help convince developers/managers of the importance of this. My only recommandation for change - I personally think there should have been more of the why before jumping into the examples. I felt like there was a little confusion from some people about why some of this refactoring was being done that didn't get explained until afterwards. But that might be just my preference.
Pretty good talk, with important reminder that your processes have a point to them and match the companies environment. Could've had more points and specifics about when and why some processes can be chucked, and a little less story time.
This talk covered a lot of things I don't know about, and was almost too dense with information. I feel this could've been split into four or five talks that dug into more of the details of each part. That's probably mostly because of my ignorance of the topic, though. Very good and interesting overview. I will definitely be going through these slides and doing a lot of research based on the information. Thanks
I found the title of this talk strange and misleading, and the talk in general was not applicable to me. There was some very good points, in particular, the importance in fixing situations where environment bugs aren't caught in dev. But if the moral of the talk was that developers should spend a year setting up their environments, I very much disagree. The more detailed this talk got, the more convinced I became that the tasks of setting up dev environments like this should not be tasked to developers. But maybe that's just me.
Very good information, very good points. I enjoyed this talk very much. I disagree with the absoluteness of the "never rewrite" rule, but I agree with the reasons behind it, and the process described was excellent. Thanks.
The title of this talk was misleading, and then it was very often off-topic from the central point. I don't think I took much away from this except that the speaker really likes Angular, and doesn't think anybody writes software correctly except himself. I found this very hard to follow, and I didn't feel like I could really ask for clarification because of how far away I was from getting it. Chock it up to me being dumb. In my opinion, there's such a thing as being too abstract, and having programming languages that are too high-level.
I was pretty surprised by the conclusion of this talk. Almost, not sure, didn't actually endorse using ADR. Feel like maybe the title of the talk might need to get revised. That being said, I thought the history of MVC and it's use within PHP frameworks was interesting. I think more important was the details of how MVC was intended. I think more emphasis on that and the ways that MVC can be done right within a web app would be good.
This got a little over-emotional for me. Almost preachy. I think this could have used a lot more focus on all the ways that software development could be focused on the user without such long, somewhat-depressing stories. I think I could have got the point from one or two brief anecdotes. Could have used more of a positive focused message with more actionable take-aways.