Some good points to tale away and think about. Felt like it went on too long though, probably as it was the last of the day.
I could only dip into this one, but Rob is the first person I've heard talk about message queues, a neglected topic.
I was very impressed with this - I hope to find lots of things to do with couchdb, and will investigate PHPillow more.
But I would suggest taking the decision out of the hands of the audience next time around, and covering PHPillow in a bit more detail, particularly at a PHP Conference.
Nothing new for me, but I could see that it was the right level for a general audience. Came alive for me when she dipped into her personal experience. More stories would have been nice.
Interesting but jumped into code too quickly, would have liked an overview/introduction to each section first.
Well worth going to - flipchart made for good variety - should have been on the other side of the room though as others said.
Some great tips.
This was the talk that covered the most stuff that I didn't know or had never heard of.
Now to find applications for it.
A very complete survey of the tools available. Icing on top would have been more advice and stories, and there was no mention of upcoming technologies. Aimed squarely at developers looking for a solution to searching their own content.
I liked this.
@PabloSerbo i'm not sure where you spotted marketing by Microsoft in this talk - I was relieved that it wasn't anything to do with Microsoft, not that I have anything against them.
We can all learn the lessons of NIH Syndrome - good keynote, right spot for the talk.
Good overview of available solutions. Would have liked to have seen an overall comparison of available features.
Great talk, amazing to see how much RM has changed his style since moving PlusNet -> iBuildings.
Loved the slides with the oldschool comics, great tools, great process advice. Will be making a lot of use of all of this shortly in my work.
Nice to see someone flying the flag for pragmatism, and testing, and good advice on what to do when you're forced to produce more legacy code based on old legacy code.
I will definitely be yoinking the term 'Technical Debt' to use in conversations with management.