AirBnB's Jack Lawson at Heroku's Waza: Dismantling the Monorail
•
1 like•841 views
AirBnB's Software Engineer Jack Lawson (@ajacksified) presented at Heroku's Developer Conference #Waza 2013 on "Dismantling the Monorail". Lawson specializes in user interface development at Airbnb, runs the SF Lua meetup group, and enjoys open-source development, building games, writing Mustache templates, and coffee connoisseurism (these interests often coincide.) He lives in San Francisco with his wife and two daughters and can be reached at @ajacksified. For more on Waza visit http://waza.heroku.com/2013. For Waza videos stay tuned at http://blog.heroku.com or visit http://vimeo.com/herokuwaza
Recommended
Recommended
More Related Content
Viewers also liked
Viewers also liked (13)
Similar to AirBnB's Jack Lawson at Heroku's Waza: Dismantling the Monorail
Similar to AirBnB's Jack Lawson at Heroku's Waza: Dismantling the Monorail (20)
Recently uploaded
Recently uploaded (20)
AirBnB's Jack Lawson at Heroku's Waza: Dismantling the Monorail
- 1. DISMANTLING THE MONORAIL Jack Lawson ( @ajacksified )
- 2. GOALS
- 3. IN THE BEGINNING A TEAM BUILDS AN APP
- 4. PRIORITY #1 RAPID ITERATION
- 7. SINGLE MVC APPLICATION LAYERS ARE GREAT THAT'S NOT SARCASM
- 8. IT'S EASYfor example risnwctam al e akra or epes-ssin -hgnctam xrs -esos -oa akra then c ctam d akra gtii i nt gtad. i d gtcmi - 'nil i omt m Ita' hrk cet eou rae gtps hrk mse i uh eou atr
- 10. KEEP IT ALL IN YOUR HEAD
- 11. LATER ON SHIFTING PRIORITIES CATKARMA A RIOTIOUS SUCCESS
- 12. TIME IS YOUR ENEMY CHAOS AND ENTROPY
- 14. HIGHER COMMUNICATION OVERHEAD MEETINGS, STANDUPS, & COORDINATION
- 16. BIG PROBLEMS IF TEST SUITE IS LACKING
- 17. UPGRADING BECOMES HARD RAISE YOUR HAND IF YOU'VE EVER PUT OFF A RAILS 3.2 UPGRADE
- 18. ONE-OFFS AND DUPLICATED CODE
- 19. TO MAINTAIN SPEED TAKE SHORTCUTS
- 22. NOT QUITE
- 24. COMPLEX AND FULL OF HACKS :(
- 25. YOU MAY ASK YOURSELF HOW DID I GET HERE?
- 26. "WE WILL REBUILD IT WHEN WE GET TIME" RIGHT? ...SOON?
- 27. DISMANTLING THE MONORAIL
- 29. A DIFFERENT CONCEPTUAL MODEL IT'S STILL SIMPLE
- 32. SERVICES
- 33. NOT A PARTICULARLY NEW IDEA YOU'RE LIKELY FAMILIAR WITH "THE INTERNET", A DISTRIBUTED SYSTEM
- 34. DISCRETE SYSTEMS LEAD TO SPECIALIZING
- 35. SPECIALIZING LEADS TO EFFICIENCY
- 37. ABSTRACTED LOGIC LEADS TO FLEXIBILITY USING THE RIGHT TOOL FOR THE JOB
- 38. BEST TECHNOLOGY FOR APPLICATION LOGIC USER INTERFACE PERSISTENCE THESE ARE ALMOST NEVER THE SAME ANSWER
- 39. REUSABLE APIS IMPLEMENT ANDROID, IOS, GOOGLE GLASSES, KINDLES, GAME CONSOLES, RASPBERRY PIS, DESKTOPS, LAPTOPS, E-PAPER WRISTWATCHES, 3-D PRINTERS, CHATBOTS, CONSOLE SCRIPTS, PUBLIC APIS... WITH NO SPECIAL CODE
- 40. PROVIDED YOU USE COMMON PROTOCOLS LIKE RESTFUL JSON
- 42. PARTIAL FAILURE MEANS THE ENTIRE APPLICATION ISN'T UNAVAILABLE
- 43. MULTIPLE SYSTEMS AT ONCE HIGHLIGHTS COMMUNICATION INEFFICIENCIES
- 44. MORE COMPLEX OPS ALLOWS SCALING SPECIFIC SERVICES
- 45. SHARED ASSETS BUNDLE REUSABLE LIBRARIES
- 46. FAST ITERATIONS WHICH IS WHAT WE WANTED ANYWAY
- 47. LESS OVERHEAD MORE EFFICIENTLY USED SERVERS AND DEVELOPER TIME
- 48. LESS FRUSTRATION STOP DIGGING THROUGH SQL INJECTED IN VIEW HELPERS
- 49. GETTING THERE FEW PEOPLE ARE STARTING FROM NOTHING
- 50. SEPARATE DATA STRUCTURES INTO LIBRARIES
- 51. DEFINE SERVICES
- 52. BREAK OUT EXISTING SERVICES INTO MODULES DEFINE AN INTERFACE, LIKE JSON OVER REST, AND REFACTOR
- 53. OPTIMIZE FEATURES INVOLVING MANY SERVICES DEFINE A VIEW IN THE MIDDLE
- 54. BREAK OUT SERVICE MODULES INTO SERVERS
- 55. DELETE YOUR OLD MONOLITHIC REPOSITORY