A look at how we can apply design patterns more commonly seen in object-oriented development to FileMaker development. In most cases they don't translate well to FileMaker development, so is there any point in even trying? We'll discuss what the real goal is here - reusable reliable code.

We'll look at a couple of examples to see whether this kind of thinking is useful in our FileMaker development. While I'll show a simple implementation of the Observer design pattern, this is going to be more of a philosophical discussion about whether the ideas have any relevance to FileMaker. Almost certainly this will trigger some good arguments and discussions and we'll all come away having learned something from each other.