the subject was interesting and showed an interesting approach at TDD. The talk itself was structured a bit too much as a workshop and this was a little boring to follow without the possibility of trying, hands on.
The talk holds a lot of information including the history of TDD which is interesting. The talk was however more focused on a workshop instead of a talk. In the end it felt like watching a video and speaker was just explaining what happened in the video.
Another point for the speaker is that he was looking constantly to the screen instead of the auditions.
Really good talk on WHY doing TDD and what is the reason of doing that. So first half of the talk - great.
But demo of the code wasn't appropriate for the audience, especially since the code couldn't be seen from further rows in the back.
Good talk and interesting points on the history of the TDD approach and what it means. The demo was nice to see an actual "real life" case, albeit maybe a bit too long.
Agree with Povilas, some good points and info in the first half, although the speaker doesn't have the most engaging speaking style, but the demo was very tough to follow in the back, I could have done with more info about why and how to use TDD instead.
The outplayed title scared me a bit, but I'm interested in the topic, so I went anyway. I really lost interest in the very long introduction with more focus on semantics than practically applicable things. Suddenly we moved to a way higher level, and I never really caught up, so I gave up about halfway through the talk.
Some interesting insights into TDD etc. As other said, examples were difficult to follow and in the end trivial. Another time would love more on when things get big and complex.
I liked the beginning a lot. It was a great overview of the history of testing and I liked the explanation of the definitions a lot. But I couldnt follow the examples. Maybe I was too far away because I was standing in the back.
This talk was moe interesting for people with experience in test-driven development (or specs). For me it went way too fast. I felt like he could have achieved more with a smaller example.
Would have wanted to see a little more actual live coding instead of explaining what is happening in a video, which was a little too fast, otherwise good talk, I learned some things :)
I'll start with the positives. I thought the first half of the talk was informative, interesting and presented really well. But considering the talk mentioned making testing fun, I don't think the second half really matched up to that.
The second half was incredibly hard to follow from where I was sitting. I don't think the room acoustics helped in that respect, but I think it could've been scheduled a lot better with just a couple of examples rather than rushing through quite a few very similar examples. I think it maybe should've concentrated on the differences/benefits against using PHPUnit for example.
The history & definition part took too long for my taste.
I liked it very much that you've done a more complex example than the standard TDD examples in other talks or tutorials. Even if I couldn't follow the implementation till the end, it was nice to see.
I had a seat in front of the stage (3rd row), so I could see the small mouse cursor in the example. But I heard very often that the people standing in the back had no chance seeing anything.
So - perhaps you could use a bigger font and mouse cursor
Comments
Comments are closed.
the subject was interesting and showed an interesting approach at TDD. The talk itself was structured a bit too much as a workshop and this was a little boring to follow without the possibility of trying, hands on.
Interesting insights about testing vs specs, but the actual explanation was a bit rushed and hard to follow.
The talk holds a lot of information including the history of TDD which is interesting. The talk was however more focused on a workshop instead of a talk. In the end it felt like watching a video and speaker was just explaining what happened in the video.
Another point for the speaker is that he was looking constantly to the screen instead of the auditions.
Really good talk on WHY doing TDD and what is the reason of doing that. So first half of the talk - great.
But demo of the code wasn't appropriate for the audience, especially since the code couldn't be seen from further rows in the back.
Good talk and interesting points on the history of the TDD approach and what it means. The demo was nice to see an actual "real life" case, albeit maybe a bit too long.
Agree with Povilas, some good points and info in the first half, although the speaker doesn't have the most engaging speaking style, but the demo was very tough to follow in the back, I could have done with more info about why and how to use TDD instead.
I liked the talk, but I would've loved to hear a shorter explanation of the author of TDD and see live coding instead of a video.
The beginning was interesting but slow, maybe something spicy in it can keep people focused and interested during the whole session.
As I have some experience with phpspec it makes things easy to understand, maybe newcomers might be lost during the screencasts.
Otherwise very good talk and I loved the quotes.
Sorry, this talk wasn't really my cup of tea. The title itself is over used (and actually used in 2014 already).
More importantly, the talk itself was hard to follow. A lot of history and quotes but rushed insights and code examples.
Lost my interest halfway through the presentation.
The outplayed title scared me a bit, but I'm interested in the topic, so I went anyway. I really lost interest in the very long introduction with more focus on semantics than practically applicable things. Suddenly we moved to a way higher level, and I never really caught up, so I gave up about halfway through the talk.
Loved it. It was like a wrap up of yesterday's workshop about DDD for me! Read code example was perfect for this presentation!
Some interesting insights into TDD etc. As other said, examples were difficult to follow and in the end trivial. Another time would love more on when things get big and complex.
I liked the beginning a lot. It was a great overview of the history of testing and I liked the explanation of the definitions a lot. But I couldnt follow the examples. Maybe I was too far away because I was standing in the back.
This talk was moe interesting for people with experience in test-driven development (or specs). For me it went way too fast. I felt like he could have achieved more with a smaller example.
very interesting and well explained.
one step went a bit fast for me: how to get from working specs to working code?
Would have wanted to see a little more actual live coding instead of explaining what is happening in a video, which was a little too fast, otherwise good talk, I learned some things :)
Didn't catch me. Maybe more interesting for people who have no idea about tdd.
I'll start with the positives. I thought the first half of the talk was informative, interesting and presented really well. But considering the talk mentioned making testing fun, I don't think the second half really matched up to that.
The second half was incredibly hard to follow from where I was sitting. I don't think the room acoustics helped in that respect, but I think it could've been scheduled a lot better with just a couple of examples rather than rushing through quite a few very similar examples. I think it maybe should've concentrated on the differences/benefits against using PHPUnit for example.
The history & definition part took too long for my taste.
I liked it very much that you've done a more complex example than the standard TDD examples in other talks or tutorials. Even if I couldn't follow the implementation till the end, it was nice to see.
I had a seat in front of the stage (3rd row), so I could see the small mouse cursor in the example. But I heard very often that the people standing in the back had no chance seeing anything.
So - perhaps you could use a bigger font and mouse cursor