I used to thinks so too, but realised that things start looking like this:

```javascriptBackbone.View.extend({
  events: {
    'click .thing-a': onThingAClick,
    'click .thing-a': onThingAChange,
    'click .thing-b': onThingBClick,
    'click .thing-b': onThingBChange,
    'click .thing-c': onThingCClick,
    'click .thing-d': onThingDClick,
  },

  ...

    onThingAClick: function() {
    ...
  },

  onThingAChange: function() {
    ...
  },

  onThingBClick: function() {
    ...
  },

  onThingBChange: function() {
    ...
  },

  onThingCClick: function() {
    ...
  },

  onThingDClick: function() {
    ...
  }
});
```

Compare that to this:
```javascript
Backbone.View.extend({
  events: {
    'click .thing-a': function() {
      ...
    },

    'click .thing-a': function() {
      ...
    },

    'click .thing-b': function() {
      ...
    },

    'click .thing-b': function() {
      ...
    },

    'click .thing-c': function() {
      ...
    },

    'click .thing-d': function() {
      ...
    },
  }
});
```

In other words, the 'table of contents' starts to become a redundant piece of code and adds bloat to the view. In my opinion, simply using `click .thing-a` is simpler and more express than `onThingAClick`. I don't think we have the time for coming to a consensus on code style at this point though, so I'll change it to the 'table of contents' style.