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
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.
Alex Gaynor explains how he solved the usual Ruby VM speed problems with Topaz, a high performance VM built on the same technologies that power PyPy.
Miles Sabin and Edwin Brady exemplify what can be done with a language with dependent types, what are the limitations and what could be done in the future when dependent types reach maturity.
Ben Johnson discusses the Raft protocol and how it works. Raft is a consensus distributed protocol.
Brendan Eich surveys interesting developments in the Web platform, analysing emergent trends, and making some predictions.
Stefan Fochler shares best practices on using Ember.js to master the needs of real-world web applications, discussing what worked well and what didn't.
Nick Kolegraff discusses common problems and architecture to support all the phases of data science and how to start a data science initiative, sharing lessons from Accenture, Best Buy, and Rackspace.
Kevin Lamping presents patterns for writing CSS for very large websites.