Object-Oriented Design Criticism

I share the criticism of Object-Oriented programming and design that I find inspiring.

Recently I've enjoyed watching: Object-Oriented Programming is Embarrassing: 4 Short Examples by Brian Will

As I'm learning Rails at the moment I enjoy seeing examples in Ruby as well.

It's easy to feel inspired by 'good architecture'. Then you go back to work. Use it in your next project. But, your project is a small website. Or a small app. Most of the architecture only makes it harder to figure out. Even worse. You write a big application. Unfortunately, your business domain is different. Maybe you need lower latency. Maybe you have 3 different teams. Maybe you write it in another language. Ther architecture you pick at the beginning is a guess. It's better to avoid guessing for as long as possible.

There is a place for good architecture. Unfortunately, it's abused most of the time.

If you don't believe in my experience take a look at quotes that summarize it well:

The design process is an iterative one.

Everything should be built top-down, except the first time.

Quotes from the great talk Procedural Programming: It’s Back? It Never Went Away - Kevlin Henney

Share on Hacker News
Share on LinkedIn

← Home

Want to learn more?

Sign up to get a digest of my articles and interesting links via email every month.

* indicates required

Please select all the ways you would like to hear from Krzysztof Kula:

You can unsubscribe at any time by clicking the link in the footer of my emails.

I use Mailchimp as a marketing platform. By clicking below to subscribe, you acknowledge that your information will be transferred to Mailchimp for processing. Learn more about Mailchimp's privacy practices here.