Skip to content

Instantly share code, notes, and snippets.

@mike-burns
Forked from matiaskorhonen/speaker.md
Created June 14, 2012 18:33
Show Gist options
  • Save mike-burns/2932034 to your computer and use it in GitHub Desktop.
Save mike-burns/2932034 to your computer and use it in GitHub Desktop.
Frozen Rails Talk Proposal Template (http://2012.frozenrails.eu/)

Mike Burns

Contact details

Speaker bio

Mike Burns plays many roles at thoughtbot, including the Haskell enthusiast, their sole Linux user, an object-oriented programmer, unix historian, and the head of the European branch. Talk with him about Scala, Android, Smalltalk, Scheme, how grep got its name, or Ruby if you must. He also has the power to accept your paperclip pull request; bribery is welcome.

When Not to Use Object-Oriented Techniques

  • Desired talk duration: 30 minutes

Abstract

Object-oriented Ruby is a hot topic in the Rails world and beyond, but it is not always the appropriate solution.

In this talk I discuss various OO techniques, when to use them, and when a simpler pattern exists in the functional, declarative, or procedural world — including, yes, the Rails framework itself. You will leave knowing when to use an aspect instead of a decorator, a mixin instead of a presenter, or a monoid instead of a factory.

Topics will include:

  • The benefits of code coupling.
  • What makes Rails so anti-OO, and why that is good.
  • Testing non-object oriented code.
  • Good uses of classical OO design patterns.
  • How to use a continuation.

Notes

Giving a similar, though opposite, talk at irb.no (the Oslo Ruby group). I have given other talks on various other topics; see my publicity page for those details.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment