David Heinemeier Hansson (DHH)

ethos of duck typing.

I don't know if you've heard that term before.

It's essentially not about, can I call this method if a object is of a certain class?

It is, can I call this method if the method responds?

It's very out of small talk in that regard.

You don't actually check of whether that

class has the method, which allows you to dynamically add methods at runtime and do all sorts of really interesting things that underpin all the beautiful metaprogramming that we do in Ruby.

I don't want to lose any of that.

And I don't care for the benefits.

One of the benefits I've seen touted over and over again is that it's much easier to write correct software.

You're going to have fewer bugs.

You're going to have less null pointer exceptions.

You're going to have less all this stuff.

Yeah, I don't have any of that.

It's just not something that occurs in my standard mode of operation.

I'm not saying I don't have bugs.

Of course I do.

But I catch those bugs with unit testing, with integration testing.

Those are the kinds of

precautions that will catch logical bugs, things that compile but are wrong, along with the uncompilable stuff.