Stop using development mode

Stop using development mode

Rails development mode is easy, useful and fast: we can spin up an app, edit its source, hit reload in a browser and see the result of our changes. But what effect does this workflow have on our code, and does it really help us? In this talk I look at the dark side of development mode — where it falls down, what it does wrong, and how it ultimately encourages us to develop software in the wrong way — and suggest an alternative way of working which avoids these disadvantages.

Given at Railsberry (http://railsberry.com/). There's a video of this talk at http://youtu.be/TQrEKwb5lR0.

Cd9b247e4507fed75312e9a42070125d?s=128

Tom Stuart

April 20, 2012
Tweet

Transcript

  1. 6.
  2. 7.
  3. 8.
  4. 9.
  5. 10.
  6. 11.
  7. 12.
  8. 13.
  9. 14.
  10. 15.
  11. 16.
  12. 17.
  13. 24.
  14. 28.

    why write tests when you can press reload? the app

    works! now write tests so you don’t feel guilty the app broke! now write tests so it doesn’t break again
  15. 31.

    write a migration write a model write a controller write

    a template write a route press reload
  16. 32.
  17. 42.

    Development mode doesn’t let you see anything working until you’ve

    completed a full vertical slice through the application.
  18. 45.
  19. 66.