I really enjoyed this talk. I had never heard of the different camps of tdd. I've only started testing fairy recently but haven't done tdd. I'm now very interested in trying it out on my next project and figure out how to use tdd to improve the design of my current app.
I thought this was a great talk. I haven't been able to get into doing TDD, but I know I need to. This gave me the inspiration to really look harder at doing TDD in the London style.
Enjoyed the philosophical discussion of testing schools of thought and in depth look at different test doubles (e.g. not everything is a "mock"). As someone who doesn't currently test, it is definitely encouragement towards at the very least implementing some testing if not implementing TDD principles.
Thank you so much Yitzchok for an incredible talk. I really like how you framed the issues of TDD, and linked it to better design. Your presentation style is excellent, and you promoted deeper understanding through the interaction you had with your audience with the discussion based talk. You have inspired me personally to investigate further the two schools (London/Chicago). I also appreciate your thoughts of starting with Classicist and getting on the road to aspire to be a Mockist. Very thought provoking! Thank you again for taking time out to share your wisdom with us here in Madison!
In order to keep the presentation to 60 minutes, I recommend shortening the "who I am" section. Most people will accept your credentials from the short bio they read prior to the talk.
Focusing on your main points and yet allowing for discussion is challenging. Therefore, keep your personal comments on what the audience is saying to a minimum, IMO.
You walked the line pretty well between being extremely opinionated but without completely throwing the other side under the bus. Great talk but very long. The buggy slides were a hiccup one might expect from the first time giving the talk. The last example of the Mock could use some work; I think that it was indeed *not* a Mock and either the original source was wrong or the porting form Java to PHP missed something. If it turns out that the example is bad (hey, everyone makes mistakes, right?) it might be an interesting thing to be able to show a real example of a Mock and then show, "this is actually what the original author did; see, even *experts* can get it wrong!"
The talk was super long. As an attendee, I find that it isn't so bad if a talk is long if you are expecting that to be the case. Otherwise, I kept wondering, "is it almost done yet?" and as it went past an hour, "how much longer?" I guess I was distracted from the talk simply by wondering when it would be done. That is mostly on me, but hey, it was an interesting position to find myself in given I've given at least one or two "hour too long" talks in the past. :)
Thanks for coming to Madison to speak with us! I'm a php newbie and this was pretty advanced for me, but I appreciated how you defined your terminology and recommended other sources, even those you disagreed with.
Comments
Comments are closed.
I really enjoyed this talk. I had never heard of the different camps of tdd. I've only started testing fairy recently but haven't done tdd. I'm now very interested in trying it out on my next project and figure out how to use tdd to improve the design of my current app.
I thought this was a great talk. I haven't been able to get into doing TDD, but I know I need to. This gave me the inspiration to really look harder at doing TDD in the London style.
Enjoyed the philosophical discussion of testing schools of thought and in depth look at different test doubles (e.g. not everything is a "mock"). As someone who doesn't currently test, it is definitely encouragement towards at the very least implementing some testing if not implementing TDD principles.
Great talk on everything from theory to implementation. I would highly recommend this talk to everyone who is interested in unit testing. Thanks -
Thank you. It was an enlightening talk. It gave me a different frame of reference to view some of my co-workers' crazy testing styles.
-- Team Chicago
Thank you so much Yitzchok for an incredible talk. I really like how you framed the issues of TDD, and linked it to better design. Your presentation style is excellent, and you promoted deeper understanding through the interaction you had with your audience with the discussion based talk. You have inspired me personally to investigate further the two schools (London/Chicago). I also appreciate your thoughts of starting with Classicist and getting on the road to aspire to be a Mockist. Very thought provoking! Thank you again for taking time out to share your wisdom with us here in Madison!
As someone who doesn't do TDD, this was very insightful. It has given me an excellent frame of reference as I begin exploring the possibilities.
Good presentation and discussion.
In order to keep the presentation to 60 minutes, I recommend shortening the "who I am" section. Most people will accept your credentials from the short bio they read prior to the talk.
Focusing on your main points and yet allowing for discussion is challenging. Therefore, keep your personal comments on what the audience is saying to a minimum, IMO.
You walked the line pretty well between being extremely opinionated but without completely throwing the other side under the bus. Great talk but very long. The buggy slides were a hiccup one might expect from the first time giving the talk. The last example of the Mock could use some work; I think that it was indeed *not* a Mock and either the original source was wrong or the porting form Java to PHP missed something. If it turns out that the example is bad (hey, everyone makes mistakes, right?) it might be an interesting thing to be able to show a real example of a Mock and then show, "this is actually what the original author did; see, even *experts* can get it wrong!"
The talk was super long. As an attendee, I find that it isn't so bad if a talk is long if you are expecting that to be the case. Otherwise, I kept wondering, "is it almost done yet?" and as it went past an hour, "how much longer?" I guess I was distracted from the talk simply by wondering when it would be done. That is mostly on me, but hey, it was an interesting position to find myself in given I've given at least one or two "hour too long" talks in the past. :)
Thanks for coming to Madison to speak with us! I'm a php newbie and this was pretty advanced for me, but I appreciated how you defined your terminology and recommended other sources, even those you disagreed with.