Skip to content

Instantly share code, notes, and snippets.

@patshaughnessy
Last active August 29, 2015 14:01
Show Gist options
  • Star 0 You must be signed in to star a gist
  • Fork 0 You must be signed in to fork a gist
  • Save patshaughnessy/b99dbf5dfbe40095d76b to your computer and use it in GitHub Desktop.
Save patshaughnessy/b99dbf5dfbe40095d76b to your computer and use it in GitHub Desktop.
Wow Justin, I really loved this! My only criticism is that it’s too bad you
used CoffeeScript instead of Ruby :)
I especially loved the top-down approach you used in your example. I’ve started
to use this all the time myself. I actually wrote about this recently:
http://patshaughnessy.net/2014/2/10/use-an-ask-dont-tell-policy-with-ruby
For me, the biggest benefit of the top-down (“Ask, Don’t Tell” - apologies to
Dave Thomas) style is how it encourages a functional coding style. There are
just so many benefits of doing this. Since I’ve been doing this at a micro
level (methods and single classes) and not with entire applications, I hadn't
thought too much about how this relates to mocking. So I loved your mocking
style and will definitely try it next time I break down a new app into pieces.
I also LOVED your line “Develop a workflow that disposes, rather than changes,
existing code.” Very insightful.
And btw fantastic screencast production work. I felt like I was watching a
conference presentation inside your office. Great job.
Anyway, thanks for the screen cast. Great work.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment