The DUDE pattern vs MVC pattern

Everyone was all like, “MVC” this, “MVC” that. The problem with trying to fit every program into an MVC pattern is that not every program fits into the MVC pattern. Not everything is going to have a view. Not everything is going to have a separate controller. Sometimes there are multiple controllers on the server and the client.

That is where I propose a new pattern. The DUDE pattern. DUDE stands for:

Data Models if necessary
User Interface if necessary
Design patterns if necessary
Event handling if necessary

Each part of the DUDE pattern is on an as needed basis. So you go into your application without any preconceived notions of how it should be built. Use your thorough knowledge, experience and design patterns to fit what you need without a term my friend Chuck Hoffman calls “overfactoring”. The only separation is between the data and the UI. Never hardcode a value(s) that can change.

This is advice for advanced programmers who have done this for years. All the newbies must follow the rules until they become familiar with the pros and cons of each approach.

The DUDE pattern vs MVC pattern

One thought on “The DUDE pattern vs MVC pattern

  1. Matt says:

    hehe,

    very good, you could add

    Always unit test to the start and have ‘A DUDE’… that almost becomes xtreme programming then ;)

    Like

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s