A Tale of Two Teams

So lets talk about two teams, both with old, messy, outdated code bases. One team chooses a framework, refactors behind the scenes, ships new features and one day have a shiny, modern code base.

The other rewrites it all, from scratch, with sprinkles of JavaScript. How did these two teams fare? In this talk we'll find out. Spoiler alert... both teams are happily using Ember today.

Transcript

1. A Tale of Two Teams
2. It was the best of times
3. It was the worst of times
8. We’ve been doing this a while
9. Some code
11. How customers felt
12. How we felt
19. Try Something New
21. Approved
22. Old New
23. Use the URL Tom
24. <a href=“/app.html#/new”>New</a> <a href=“/app.aspx”>Old</a> Old New
27. Don’t Care How I Want It Now
29. New Code Slipped in a few extra Tomsters
30. There are some downsides
31. The dreaded flash of white
32. Continuity
36. Still waiting on that new software.
37. Throwing it all away
38. ? Ne
40. <button onclick=“alert(‘hi mom…’)”>
44. ember provides best practices
45. guides
47. Start Here
48. WORKFLOW
49. Traditional
53. Dropping the Baton
56. ? Ne
57. New Code More Shipping
58. New Code More Shipping
59. ? Ne Ne Ne
60. ? Ne Ne Ne
61. Getting derailed
62. Getting off the Ember Train
63. More like a tourist visit
64. Ember Train was Waiting
65. Some assembly required
66. ? Ne Ne Ne
67. Seeing the Tomster
68. Swimming up stream
74. <iframe src=“/app.aspx”> </iframe>
75. postMessage(‘done’)
77. ? Ne Ne Ne
78. ? Ne Ne Ne
80. Still waiting on that new software.
84. Why?
85. Fear
87. technical debt is success
91. projects
95. ember’s conventions grow with you
96. Opinions and Flexibility are not correlated
97. Building with No Conventions
98. Building with Conventions
99. Conventions Scale
100. Return on investment 300 600 900 1200
101. Thanks! @raytiley
102. ! Give @rwjblue a beer