View presentations by conference
- QCon New York 2013
- Cloud East 2013
- ACCU 2013
- Code Generation Cambridge UK 2013
- ETE 2013
- Clojure/West 2013
- QCon London 2013
- SyncConf 2013
- DevNexus 2013
- API Strategy&Practice 2013
- Joy of Coding 2013
- CodeMash 2012
- QCon London 2012
- CodePaLOUsa 2012
- Clojure/West 2012
- Code Generation Cambridge UK 2012
- Erlang Factory 2012
- GoTo Copenhagen 2012
- QCon New York 2012
- IEEE SES 2012
- Cloud East 2012
- Mobile East 2012
- Throne of JS 2012
- Agile Culture Conference 2012
- SOA-Cloud Service Technology Symposium
- StrangeLoop 2012
- Agile Cambridge UK 2012
- Cloud Tech III
- SpringOne 2GX 2012
- SDEC 2012
- AgilePalooza New York 2012
- SPLASH 2012
- FP Days Cambridge 2012
- QCon San Francisco 2012
- Agile Tour Toronto 2012
- UX Cambridge UK 2012
Floyd Marinescu shares how the team behind InfoQ.com and QCon has managed to attain Purpose, Autonomy, and Mastery while working completely virtually for over 7 years.
Maxime Chevalier-Boisvert discusses making dynamic languages faster providing various examples of optimizations: SmallTalk, LISP machine, Google V8 and others.
Cameron Barrie, James Brett, Stewart Gleadow share lessons learned using Agile methodologies to build an iOS application, discussing its architecture and the benefits of hybrid apps.
Jim Driscoll discusses using ADFm to create and change Groovy scripts at runtime and debugging a live system with JWDP.
Kyle Boon reviews 3 frameworks for building RESTful WS- Grails, Dropwizard and Ratpack-, comparing their code readability, maintainability, deployment, metrics collection, scalability and testability.
Sergey Bolshchikov discusses building complex UIs with Ember.js by combining Handlebars templates and Ember.View.
Jeff Scott Brown discusses Groovy’s compile time metaprogramming capabilities.
Mike Krieger discusses Instagram's best and worst infrastructure decisions, building and deploying scalable and extensible services.
Bill Yetman and Jeremy Pollack discuss using several Agile techniques -start simple, get going, iterate- and the “measure everything” principle to create the architecture behind the Family History website.
Greg Brockman shares Stripe's principles powering their software projects and the culture instilled to avoid the usual software engineering traps: failed rewrites, delayed timelines, etc.
Bikas Saha and Arun Murthy detail the design of Tez, highlighting some of its features and sharing some of the initial results obtained by Hive on Tez.