Code natural selection

A funny thought just came to me: if you write nice clean code, it’s easy to replace it. Just plug out an object somewhere, replace it with another one implementing the same interface, run the tests. Tada! On the other hand, if you write crappy code it might be nigh impossible to replace it. It will probably be worked around whenever a change is needed, simply adding layers of crust. Maybe that’s why legacy code sucks: it’s simply code natural selection – and the fittest to survive is simply the crappiest one. I think I’m depressed now.


One Comment on “Code natural selection”

  1. Adar says:

    You can look at it from the other side: nice code is more likely to be replicated and used in more projects.

Leave a Reply

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

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

Google+ photo

You are commenting using your Google+ 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 )


Connecting to %s