Covered a lot of material at an overview level, where the developers have references to get more detailed info in the areas that they need to do a better job. I was disappointed in his comments about how to provide estimates. He doesn't consider that the coder doesn't realize they don't have all the requirements, that a task can be more complex than it seems, and the amount of experience the coder has with that business logic or framework or other tools being used for this particular project.
Lots of great and practical advice well presented. I especially liked the comments about making sure your code is understandable for others so that you ARE replaceable (So you can go on vacation or get promoted.)
Great, informative listing of various performance introspection and external testing systems, including real-world examples using both open-source and for-pay options.
Solid points, and enough dogma to be applicable to real-life rather than theory.
great now I have to buy another book.... ;)
Some of the content was more applicable to API usability then development: example soap vs rest endpoints was oversimplified and factually incorrect.
Engaging talk with a lot of good information presented concisely. Familiarity with audience presented a feeling of interactivity.
I may disagree with some of the things stated (maybe my coder bias), but the talk was both informative and engaging.