Talk comments

Personally I'd have liked to have seen some code examples since I was already familiar with the concept of queues. James should perhaps have prepared a bit better so that he didn't need to use his phone :P

This talk really helped me understand BDD and also agile better. Konstantin delivered the talk at a very easy going pace and at a level that everyone understood. I would be interested in hearing a more in-depth talk about Behat.

James took us through what the RabbitMQ does and what you can get out of it, with easy to follow diagrams. I found the comments (possibly in the questions) about what it does if one of the servers is offline interesting, because it was good to hear how it did its job as well.

This was a *really* good talk. The content was really relevant to what we're doing and is likely to have a big impact on how we do it.

Well explained and paced nicely. Konstantin gave easy to follow examples, and the visual aids showed you clearly how it all fit together in the bigger scheme of things. There were useful points to take away that weren't dependent on specific technology, making this hopefully accessible to all levels of expertise.

A brilliant quick fire introduction into what rabbit MQ can bring to the table. We are considering implementing a Stats D based logger but James has helped us reconsider using a queue to manage application logging. Would be nice to see some more comparisons with {INSERT_HERE} queue managers :)

Konstantin presented an inspiring talk on BDD practices. It was a good introduction on how to useful BBD can be as a communication tool. Some of the slides were hard to see as the text was in a pale yellow and blue colour but this may of been the projector. Thank you Konstantin, this is something we'll be looking at soon!

Anonymous at 09:36 on 10 Apr 2014

The talk was surprisingly good. Rather than focusing on tools, it explained what BDD is why you'd use it. Even if you never planned to use behat / phpspec or even automate testing, you'd still learn from this presentation.

Konstantin gave me a brilliant insight as to what BDD really means - it's certainly not what I thought it was about. BDD is really a communication methodology, rather than a development practise. He went into detail on how this could be put into practise in the real world, which was important - and it wasn't too technical either, which I think meant that this was helpful to many people. There was some interesting discussion at the end too in the questions time, which really added to the talk.