Get Started. It's Free
or sign up with your email address
Craft by Mind Map: Craft

1. original ideas

1.1. Boxen (Github?)

1.2. QuickCheck (Basho?)

1.3. Riak2

1.4. cool HTML5 tpoic

1.5. Distributed system design

1.6. Programming tools

1.7. FRP

1.8. API design

1.9. Test-First Construction of Distributed Systems (Joseph Blomstedt)

1.10. Micro services

1.11. WebRTC & XMPP

1.12. NewSQL

1.13. InfoQ - Facebook Director of Egineering

1.14. MapReduce design patterns

1.15. JetBrains MPS


1.17. online engineering tools

1.18. erlang factory talk

1.19. elixir


1.21. infrastructure continuous delivery




1.25. platforms (typesafe, pivotal, springbasz, netflix ec2 stuff)

1.26. Quite interesting graph database stuff:

1.27. NOSQL overview, how to choose?

1.28. Baron Schwartz - monitoring

1.29. Michael Kopp -


1.31. Web Components

1.32. Joe Armstrong - Systems that Run Forever Self-heal and Scale



1.35. Tariq Sami -

1.36. Miško Hevery - AngularJS design

1.37. Culture of innovation

1.38. Handling distributed teams


1.40. Emphasising learning in a team

1.41. Information sharing

1.42. Scaling development

1.43. Organisational best practices

1.44. Lean Startup: AB testing, MVP etc.

1.45. Devops as company culture

1.46. Real Options

1.47. Rx, RxJava

1.48. Sonar / SonarQube

1.49. Ariya Hidayat - Esprima

1.50. Mocking, Spys etc.

1.51. SOA

1.52. Unit test vs acceptance test

1.53. TDD traps, mistakes

1.54. Kanban

1.55. Code kata, code retreat

1.56. Salt Stack

1.57. d3.js

1.57.1. Makoto Inoue

1.58. pragmatic programmer

1.59. wooga - culture

1.60. Complexity theory

1.61. Domain specific languages

1.62. Correctness verification (

1.63. Polyglot Architecture (

1.64. Andreas Zeller (

1.65. Software verification

1.66. Software architecting (

1.67. hypermedia api

1.68. scala

1.69. facebook security guy

1.70. Are Your Lights On?: How to Figure Out What the Problem Really Is

1.71. Berkshelf


1.73. LXC,


1.75. Pete Hunt talk about React

1.76. VividCortex

1.77. A Whole New Mind: Why Right-Brainers Will Rule the Future

1.78. Marc-André Cournoyer: Creating your first programming language

1.79. node.js cluster bigyók

1.80. Stephen Vance - Quality Code: Software Testing Principles, Practices, and Patterns

1.81. Marc Planagumà – Cicerone: A Real-Time social venue recommender

1.82. Kevin Scott:

1.83. Raymond Roestenburg on Akka in Practise: designing actor-based applications

1.84. Paul Duvall -

1.85. Philippe Kruchten - Director of Process Development (RUP)

1.86. Matt Heusser - "The Great Game of Testing"

1.87. Structured refactoring

1.88. Bret Victor - The Future of Programming

1.89. Vaughn Vernon -

1.90. Performing Code Katas -


1.92. Design Principles of Angular.js (?)

1.93. Netflix - EC2 toolset (?)

1.94. CloudFoundry/BOSH




1.98. First, Kill All the Product Owners

1.99. I also had an interesting conversation with Ted Neward at JAX London about everything that's wrong with Software Craftsmanship - might be worth getting him along to talk about that.

1.100. Kevin McGuire


1.102. David Louvton, Amool Gupta, The Selenium Infrastructure at Salesforce

1.103. Holistic cross-browser testing with Selenium, RedGlass and DomReactor

1.104. Linus Torvalds

1.105. Kent Beck

1.106. James Gosling

1.107. Bjarne Stroustrup

1.108. Grady Booch

1.109. Erich Gamma

1.110. Roy Osherove


2. idea pool

2.1. agile

2.1.1. Agile Metrics Michael Norton

2.1.2. No manager approach (Valve, Github, Joyent) Bryan Cantrill

2.1.3. Kanban Benjamin Mitchell

2.2. api

2.2.1. Redesign Paypal Deepak Nadig , Praveen Alavilli Netflix Daniel Jacobson

2.2.2. Realtime Ross Mason

2.2.3. Reactive Jafar Husain

2.2.4. API Security and Federation Patterns François Lascelles

2.2.5. CQRS Anders Ljusberg

2.2.6. API Blueprint Jakub Nesetril

2.3. team

2.3.1. (Neuro) Science Peter Saddington

2.3.2. Work -> Paly Portia Tung

2.3.3. Improving teams Sven Peters Jesper Richter-Reichhelm

2.3.4. Culture Greg Brockman Patrick Collison

2.3.5. Learning Matthew Barcomb

2.4. architecture

2.4.1. Continuous Architecture Scott Ambler

2.4.2. Layers Considered Harmful Christian Horsdal

2.4.3. Microservices Kevin Scaldeferri James Lewis Sam Newman

2.4.4. Fault tolerance Uwe Friedrichsen

2.4.5. CQRS Oliver Wolf

2.4.6. Realtime Systems Hilary Mason

2.4.7. Rapid Release Sam Newman

2.4.8. SOA August Lilleaas Ben Christensen

2.4.9. Real World Polyglot Persistence Jimmy Bogard

2.4.10. noBackend Gregor Martynus Michiel B. de Jong

2.4.11. The Architecture of Uncertainty - Kevlin Henney

2.5. CI/CD

2.5.1. Use case Outbrain - Itai Hochman - Yoav Abrahami Heroku - John Simone eBay, Google - Randy Shoup Google - Eran Messeri Expedia - Igor Dorovskikh, Kaustubh Gawande Facebook - Christian Legnitto

2.5.2. Using cloud Edmund Haselwanter Roy Rapoport (Netflix)

2.5.3. Mobile Spotify - Per Eckerdal, Mattias Björnheden

2.5.4. Infrastructure Vagif Abilov Carlos Sanchez

2.5.5. Architecture Andreas Grabner

2.6. cloud

2.6.1. Azure Nuno Filipe Godinho

2.6.2. Netflix OS PaaS components Sudhir Tonse Adrian Cockcroft

2.7. database

2.7.1. Use case Riot Games: MySQL -> Riak - Garrett Eardley Mail.Ru: Tarantool - Konstantin Osipov

2.7.2. Graph Computing Matthias Broecheler Jim Webber

2.7.3. NoSQL DB comparison Ben Engber

2.7.4. MySQL as NoSQL - Ted Wennmark

2.7.5. NewSQL Peter Almquist

2.8. devops

2.8.1. Next setp Andrew Clay Shafer

2.9. distributed

2.9.1. R2D2 - Oby Sumampouw, David Hoa

2.9.2. Erlang - Omer Kilic

2.9.3. CRDT - Richard Shaw

2.9.4. Eventual Consistency - Matt Heitzenroder

2.9.5. Samza - Chris Riccomini

2.9.6. Jeff Hodges

2.10. functional programming

2.10.1. Parallel programming Kevin Hammond Erik Stenman

2.10.2. End to end Reactive Programming - Jafar Husain

2.10.3. Java 8 Joshua Suereth Brian Goetz

2.10.4. Functional Architecture - Phil Trelford

2.10.5. Deconstructing Functional Programming - Gilad Bracha

2.10.6. Better JavaScript with FP - Phil Calcado

2.10.7. Reactive Javascript Jafar Husain

2.11. java

2.11.1. Memory Leak - Nikita Salnikov-Tarnovski

2.11.2. Java Flight Recorder Rickard Bäckman

2.11.3. Troubleshooting Live Java Web Applications Ashley Puls

2.11.4. JMX Tom Lubinski

2.12. language

2.12.1. Taking PHP Seriously - Keith Adams

2.12.2. Deep C++ - Olve Maudal

2.12.3. Superconductor DSL - Leo Meyerovich

2.12.4. The Art of Building Tools - Markus Voelter

2.12.5. Elixir

2.13. misc

2.13.1. Creative Machines - Joseph Wilk

2.13.2. Intel's Next Generation Microarchitecture Codename Haswell - Ravi Rajwar

2.14. mobile

2.14.1. Device Fragmentation Chiu-Ki Chan

2.14.2. Testing at Facebook Simon Stewart

2.14.3. Application Performance Doug Sillars

2.14.4. Web vs. Native Andrew Betts

2.15. performace

2.15.1. Web caching techniques Wim Godden

2.15.2. Integrating P to the process Ivan Filho

2.16. platform

2.16.1. The Hip Hop Virtual Machine - Andrei Alexandrescu

2.16.2. JVM

2.16.3. Typesafe

2.16.4. Pivotal

2.17. programming

2.17.1. Visualization Driven Development - Jason Gilman

2.17.2. Scala Async Philipp Haller

2.17.3. Code as a crime scene - Adam Petersen Tornhill

2.17.4. The ideal module system and the harsh reality - Adam Warski

2.18. security

2.18.1. Automated XSS detection - Claudio Criscione

2.18.2. James Wickett

2.18.3. Ahto Truu Efficient Record-Level Signing for Logs Protecting Your Data with Keyless Signatures

2.18.4. Redesigning the Computer for Security - Tom Hawkins

2.18.5. Web Cryptography API Nick Van den Bleeken

2.18.6. Anders Skovsgaard

2.18.7. Warm Up to Identity Protocol Soup - David Waite

2.19. testing

2.19.1. Use case Twitter - James Waldrop Unity Technologies - Dmytro Mindra

2.19.2. Testable JavaScript - Mark Trostler

2.19.3. Spock & Geb Luke Daley, Peter Niederwieser

2.19.4. Effective mocking Venkat Subramaniam

2.19.5. Test-Driven JavaScript Master Class - James Shore

2.19.6. Good test design Katya Mustafina Ian Cooper

2.19.7. Sonar Patroklos Papapetrou

2.20. web

2.20.1. Concurrency and Parallel Computing in JavaScript Stephan Herhut

2.20.2. JavaScript Code Complexity Jarrod Overson

2.20.3. Meteor Matt Debergalis

2.20.4. SocketStream Owen Barnes

2.20.5. HTTP 2.0 Roberto Peon

2.20.6. Realtime Gabriel Grant

2.21. ux

2.21.1. Seeing and touching: your mobile brain - Chris Atherton

2.21.2. Monitoring UI performance - Eric Perret

2.21.3. Continuous Experimentation - Frank Harris & Nell Thomas


3. speakers

3.1. agile

3.1.1. Tom Gilb Advanced Agile Practices: The Evo Method in practice

3.1.2. Simon Brown ebook: Software Architecture for Developers Sustainable competence - the people vs process and technology Effective Architecture Sketches The Conflict Between Agile and Architecture: Myth or Reality? Software architecture and the balance with agility

3.1.3. Liz Keogh [email protected] Don't let your process hide your ignorance Behavior-driven Development Behavior-Driven Development for Life

3.1.4. Lisa Crispin? Growing whole teams using the Dreyfus model The Whole Team Approach The Whole Team Approach to Testing

3.1.5. Jurgen Appelo Complexity Thinking Management 3.0 The 7 Duties of Great Software Professionals What Is Agile Management? Management 3.0 - Empower Teams Complexity versus Lean

3.1.6. Geoff Watts Measuring Agile Team Maturity The Seven Pillars Of Collaboration - Why agile teams need HISTORY in order to collaborate How simple maths and BELIEF can help you coach people to change

3.1.7. Gabrielle Benefield? Stop Building The Wrong Product Righter Build The Right Product - Gabrielle Benefield Frankenbuilds; if Agile is so good, why are our products so bad?

3.1.8. Ed Kraay How to change as a manager from an expert to a coach

3.1.9. Dan North [email protected] Patterns of Effective Teams Simplicity: the Way of the Unusual Architect

3.2. api

3.2.1. Steve Klabnik? [email protected]

3.2.2. Mike Amundsen [email protected] [email protected] Designing and Implementing Hypermedia APIs Generic Hypermedia and Domain-Specific APIs: RESTing in the ALPS Hypermedia-Oriented Web Services: From APIs to Affordances REST, And Now for Something Completely Different

3.2.3. Joshua Bloch How to Design a Good API and Why it Matters

3.2.4. Ian Robinson test driven api, soa, etc.

3.2.5. Daniel Jacobson [email protected]

3.3. architecture

3.3.1. Trisha Gee [email protected] Disruptor Schema Design Design is a Process, not a Document

3.3.2. Nathan Fritz? [email protected]

3.3.3. Michael T. Nygard Exploiting Loopholes in CAP Architecture Without an End State Reliability Engineering Matters, Except When It Doesn't Failure Comes in Flavors - Stability Anti-patterns Request Path Mapping Chef in the Cloud and On the Ground Disband the Deployment Army

3.3.4. Jessica McKellar Architecting an Event-driven Networking Engine: Twisted Python The Future of Python - A Choose Your Own Adventure [email protected]

3.3.5. Forrest Norvell? Thinking asynchronously

3.3.6. Douglas Crockford Which Way Is Forward? Managing Asynchronicity with RQ

3.3.7. Code Hale

3.3.8. Alistair Cockburn Agile and Software Engineering in the 21st Century CQRS Disciplined Learning

3.4. CI/CD

3.4.1. Rachel Laycock Architecture and Collaboration the cornerstones of Continuous Delivery Pair Programming, the good, the bad and the ugly Polygot Architecture for Rapid Release: Friend or Foe? Adopting Continuous Delivery: Adjusting your Architecture

3.4.2. Jez Humble Adopting Continuous Delivery (Re-)architecting for Continuous Delivery DevOps Metrics - It's Not Just For WebOps Any More!

3.4.3. Gareth Rushgrove

3.4.4. Gareth Bowles [email protected]

3.4.5. Dianne Marsh From Code to Monkeys: Continuous Delivery at Netflix

3.4.6. David Mortenson Scaling Facebook engineering

3.4.7. David Louvton Selenium at Salesforce

3.4.8. Damien Sereni Selenium at Facebook

3.5. culture/organisation

3.5.1. Omer Shapira LinkedIn QEI - Development at Scale

3.5.2. Bryan Cantrill

3.5.3. Ashe Dryden The Diverse Team: Healthy Companies, Progressive Practices [email protected]

3.5.4. John Willis? Devops, culture Culture as a Strategic Weapon

3.5.5. Jesse Robins Devops, Changing Culture, Making Awesome

3.5.6. Gene Kim devops

3.6. database

3.6.1. Stuart Halloway Exploring Datomic: A Database Deconstructed The Impedance Mismatch is Our Fault Concurrency in Clojure

3.6.2. Stefan Edlich How NoSQL fits in a polyglot persistence world NoSQL in 5+ years Choose the "Right" Database and NewSQL: NoSQL Under Attack

3.6.3. Salvatore Sanfilippo? A short term plan for Redis Redis Cluster

3.7. devops

3.7.1. Tim Lossen Devops: next step

3.7.2. Theo Schlossnagle How Do You Eat An Elephant? Next Generation Monitoring of Large Scale Riak Applications Monitoring and observability It's all about telemetry

3.7.3. Mitchell Hashimoto Develop and Test Configuration Management Scripts with Vagrant Vagrant Usage Patterns Advanced Vagrant Usage with Puppet Automated Multi-Platform Golden Image Creation, Unlocking New Potential

3.7.4. Ken Cochrane Docker

3.7.5. John Allspaw Resilience/Automation

3.7.6. Baron Schwartz VividCortex

3.7.7. Jackson Gabbard Facebook tools and infrastructure, by hand Engineering Design for Facebook How we made faster

3.8. distributed

3.8.1. Steve Vinoski Objects, Anomalies, and Actors: The Next Revolution Innovation: What Every Developer Absolutely Needs to Know Webmachine: A Practical Executable Model for HTTP Building Distributed Systems with Riak Core Mythbusting Remote Procedure Calls Benefits and Challenges of Implementing Riak in Erlang

3.8.2. Sean Cribbs? [email protected] Data Structures in Riak Fear no more: Embrace eventual consistency Just Open a Socket - Connecting Applications to Distributed Systems

3.8.3. Nikita Ivanov GridGrain In-Memory Computing: Facts and Myths Pearls of Distributed Programming: Scala + GridGain Streaming MapReduce with GridGain and Scala

3.8.4. Neha Narula Smarter Caching With Pequod Executing Queries on a Sharded Database Executing Web Application Queries on a Partitioned Database Sharding and Scaling Your Database

3.8.5. Nathan Marz Storm, Cascalog Human fault-tolerance Runaway complexity in Big Data... and a plan to stop it Your Code is Wrong

3.8.6. Matt Ranney Real-world realtime: performance and high availability at Voxer Riak at Voxer Node-Redis [email protected]

3.8.7. Kyle Kingsbury Rieman etc. Call Me Maybe: Carly Rae Jepsen and the Perils of Network Partitions Partitions for Everyone!

3.8.8. John Ousterhout Raft: The Understandable Distributed Consensus Protocol Ben Johnson

3.8.9. Dominic Tarr Mad Science Architectures for Totally Distributed Applications. What is scalability, anyway? data, events, streams at webrebels 2013

3.8.10. Camille Fournier ZooKeeper

3.8.11. Andy Gross

3.8.12. Alvaro Videla RabbitMQ

3.9. functional programming

3.9.1. Rich Hickey The Functional Database Deconstructing the Database Core.async - Communicating Sequential Processes using Channels, in Clojure The Language of the System

3.9.2. Viktor Klang Reactive Streams Concurrency – The good, the bad, the ugly Akka 2.0: Scaling Up & Out With Actors

3.9.3. Neal Ford 5 Reasons You Should Care about Functional Programming Abstraction Distractions Functional Thinking

3.9.4. Martin Odersky Types, Scala etc. Working Hard to Keep It Simple The Trouble With Types

3.9.5. Katie Miller? Monads to the Rescue Higher-Order Fun

3.9.6. Jonas Bonér Scala 2.11: The Foundation for a Reactive Platform Going Reactive: Event-driven, Scalable, Resilient and Responsive Systems

3.9.7. John Hughes QuickCheck Certifying your car with Erlang Race Conditions, Distribution, Interactions--Testing the Hard Stuff and Staying Sane

3.9.8. Joe Armstrong Fault Tolerance 101 What are the important ideas in Erlang? Erlang was the solution - but what was the problem?

3.9.9. Evan Czaplicki A good FRP introduction

3.9.10. Erik Stenman Erlang Scales - Do You? The Erlang VM or How i stopped worrying and started loving parallel programming

3.9.11. Bodil Stokke Programming, Only Better

3.10. language

3.10.1. Torben Hoffmann Erlang still evolves for multi-core and cloud environments Erlang and the Chasm Mission Critical with Erlang And QuickCheck: Quality Never Sleeps

3.10.2. Scott Meyers An Overview of the New C++ (C++11) Effective C++11 Programming Better Software - No Matter What The Consistency Conundrum

3.10.3. Julien Verlaguet Analyzing PHP statically Moving faster with PHP at Facebook They use OCaml for this, so it can be interesting even from FP point of view.

3.10.4. Damian Conway dami[email protected]

3.11. misc

3.11.1. Zed Shaw? The Imaginative Programmer It's Not You, It's Them: Why Programming Languages Are Hard To Teach The Web Will Die When OOP Dies The Top 10 Ways To Scam The Modern American Programmer

3.11.2. Ward Cunningham? Federated wiki Information sharing Knowledge management

3.11.3. Todd Montgomery Mechanical Sympathetic Networking Building a Next Generation Messaging Architecture

3.11.4. Stefan Tilkov Web Development: You're Doing it Wrong Unlearning OOP: How to Design Clojure Programs ROCA: Resource-oriented Client Architecture

3.11.5. Poul-Henning Kamp Entirely predictable failures ESO Extremely Large Telescope: Real Time Control for Adaptive Optics with FreeBSD

3.11.6. Paul Butcher

3.11.7. Miško Hevery Angular JS design principles Psychology of Testing Test Driven Development in Angular A Radically Different Way of Building AJAX Apps

3.11.8. Margo Seltzer Automatically Scalable Computation

3.11.9. Kate Matsudaira

3.11.10. Jutta Eckstein The Art of Learning and Mentoring Complex Projects aren't plannable but controllable

3.11.11. Jonathan Berger? Code Literacy for Non-Programmers

3.11.12. John Carmack? He had a great keynote on Quakecon 2013

3.11.13. Johan Bergström

3.11.14. Joel Spolsky?

3.11.15. Joanna Zweig Discovery Curves, Group Learning and Delivering

3.11.16. Jean-Paul Schmetz? Dealing with complexity

3.11.17. Isaac Schlueter Node streams

3.11.18. Greg Young?

3.11.19. Floor Drees? The best programmers are teachers How to Learn by Teaching

3.11.20. Brian Marick? Programming with the Automatic Part of Your Brain When smoothing wood with a hand plane (craftsmanship!), you should always work with the grain rather than against the grain. It's becoming increasingly clear that what we normally think of as rationality is fairly rare. Much of what we do is governed by our brain operating on autopilot. Reasoning is the expensive stop-gap our brain uses (sometimes!) when the cheaper solution isn't working right. Programming is typically seen as an occupation that requires thoughtful precision and rationality: we will work against the grain of our brain. The resulting nicks and chips are only evidence that we should try harder! What if we instead train the automatic part of the brain to do what we want - to simply react appropriately? In this talk, Brian Marick will discuss how he tries to do just that.

3.11.21. Bjorn Freeman-Benson Some Considerations for Scaling: What We Did At New Relic "software psychologist" "Watching @bjorn_fb from @newrelic talk about the psychology of platforms!" Productivity, people management

3.11.22. Bertrand Meyer Software verification

3.11.23. Aral Balkan? Design thinking + open source [email protected]

3.11.24. Anna Obukhova Neuroscience How Scrum boosts your willpower and productivity

3.11.25. Amber Case? Cyborg Anthropology and the Future of the Interface [email protected]

3.11.26. Alissa Pajer Category Theory [email protected]

3.11.27. Alex Payne Building Teams and Selecting Technology

3.12. mobile

3.12.1. Iris Daniela Classon? Windows Phone 8

3.13. performance

3.13.1. Steve Souders web/mobile performance

3.13.2. Michael Klepikov Developer-Friendly Web Performance Testing in Continuous Integration Web Performance Testing with WebDriver Automated Web App Performance Testing Using WebDriver

3.13.3. Martin Thompson Learning and unlearning about Java performance Lock-free Algorithms for Ultimate Performance Mechanical Sympathy Top 10 - Performance Folklore

3.13.4. Gil Tene JVM mechanics: a peak under the hood Enabling Java in Latency Sensitive Environments

3.13.5. Dustin Whittle? Performance Testing Crash Course

3.13.6. Bogdan Vulcan, Gabriele Petrone? Fast By Design

3.14. platform

3.14.1. JVM

3.14.2. Pivotal

3.14.3. Typesafe

3.14.4. OpenStack

3.14.5. James Ward Building Reactive Apps with Play Framework, Akka, and Scala

3.14.6. Adrian Cockcroft Netflix's EC2 tool set Architectural patterns for high availability High Availability Architecture and NetflixOSS

3.15. security

3.15.1. Parisa Tabriz Google Chrome Security Multi-device security Chrome Security Secret Sauce

3.15.2. mimeframe [email protected]

3.15.3. Bruce Schneier security

3.15.4. Adam Baldwin Security

3.15.5. Aaron Bedra Security [email protected]

3.16. software craftsmanship

3.16.1. Uncle Bob Principles of Component Design Agile Principles Patterns Practices & Planning Clean Architecture and Design

3.16.2. Steve Yegge GROK - Large-Scale, Cross-Language source analysis. Dynamic Languages Strike Back Scalable Programming Language Analysis

3.16.3. Steve Freeman Growing Object-Oriented Software, Guided by Tests Modern Java Programming with Steve Freeman Test-Driven Development: That's not what we meant Higher Order Logic - Fractal TDD Building on SOLID Foundations

3.16.4. Sandro Mancuso? Think You Don't Need Software Craftsmanship? Curing Agile Hangover: Sandro Mancuso and Mashooq Badar Software Craftsmanship

3.16.5. Russell Miles You are not (only) a software developer! - Simplicity in practice Building the Right Thing by Applying Simplicity: Impact Mapping in Action Architectural Simplicity through Events: A war story of managing the challenge of integration and flexibility Without Simplicity, there's just no Agility

3.16.6. Nat Pryce Stop Refactoring! Brownfield to Green Test-Driven Development of Asynchronous Systems Growing Real Systems Guided by Tests

3.16.7. Michael Feathers A Type Driven Approach to Functional Design Reducing Technical Debt Patterns of Software Change Technical Debt, Process and Culture The Design Principle that sneaks through your code, your system, and your life Moving toward Symbiotic Design Through The Looking Glass - Applying Analytics to Development

3.16.8. Martin Fowler Schemaless data structures The Evolving Panorama of Data Meta-Introduction to Domain Specific Languages

3.16.9. Jevgeni Kabanov Import Continuous Delivery Data-Driven Software Engineering

3.16.10. Gojko Adzic Make Impacts, Not Software Impact Mapping: New frontier for agile planning Reinventing Software Quality

3.16.11. Gerard Meszaros

3.16.12. Eric Evans

3.16.13. Dave Thomas Unknown Knowns

3.16.14. Chet Hendrickson? Nature of Software Development

3.16.15. Chad Fowler The Passionate Programmer How to become accomplished [email protected]

3.16.16. Bruce Eckel

3.16.17. Barbara Liskov? The Power of Abstraction

3.16.18. Andy Hunt "topics from best practices in agile software development, to pragmatic programming, to teamwork, teambuilding and cognitive skills." [email protected]

3.17. web

3.17.1. Tomomi Imura HTML5 Evangelist

3.17.2. Szabolcs Toth Javascript Module Server

3.17.3. Sam Dutton WebRTC Chrome Developer Tools Media APIs for the multi-device web Realtime communication with WebRTC

3.17.4. Paul Irish Anything :)

3.17.5. Mate Nadasdi It's never too late to fight your legacy!

3.17.6. Mikeal Rogers? The Death of REST Beyond Realtime

3.17.7. Kiran Prasad Lessons from building LinkedIn Mobile - HTML5 & Node.js Mobile: Past, Present, Future — Tech Choices and Architecture Impact

3.17.8. Ilya Grigorik HTTP 2.0

3.17.9. Feross Aboukhadijeh PeerCDN - WebRTC [email protected]

3.17.10. Divya Manian Layouts in CSS Web Components with your favourite CSS specs Creating Web Experiences with users in mind

3.17.11. Dio Synodinos Book: Pro HTML5 and CSS3 Design Patterns

3.18. tools

3.18.1. Craig Muth

3.18.2. Chris Granger Finding a Way Out I have a basic premise: we didn’t nail programming 40 years ago. Instead, I believe there’s something different waiting for us out there, something better. And while people like Alan Kay and Charles Simonyi have been hinting at it for decades, we’re still here with our text editors desperately trying to gain insight into the twisted messes we’ve created. For the longest time we’ve gained power at the cost of complexity, but at some point we have to find our way out of the maze. A new language isn’t enough. Even new tools like Light Table only suggest a path forward. To truly escape, we have to take a step back and re-imagine what it means to create software. We have to let go and ask ourselves – what would programming look like if we created it today?

3.18.3. Anna Powell-Smith D3.js

3.19. ux

3.19.1. Gócza Zoli ux product idea validation

3.19.2. Chris Atherton Seeing and touching: your mobile brain In this talk, Chris will give an overview of how the brain processes visual information, and in what order. She'll demonstrate that the human visual system is fickle and can be tricked, and talk about the implications of this for software design. Chris will also explore the idea that mobile devices have become an extension of our cognitive space, and consider whether it really matters that most of us no longer memorise people's phone numbers. She'll also cover our physical and emotional relationship with phones and other mobile devices, and discuss some of the reasons why we might be so attached to our "outboard brains".