Build to last.

Will your code stand the test of time?

If you write your code well, people will still be using it twenty years from now. If you write it poorly, other developers will look to refactor and replace it at their first opportunity. To save them that work, it’s much better to write reliable code that future developers won’t need to rewrite anytime soon.

One reason programmers replace code is needless complexity. They find the existing software to be confusing, hard to understand, and difficult to change. Instead of extending it or improving it, they find it easier to replace it entirely. Software that lasts tends to be elegant in its simplicity. Future developers can understand the long-lasting code at a glance. It follows popular conventions and doesn’t try to do anything weird or clever.

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 )

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

%d bloggers like this: