Only Solve Hard Problems When You Have To

Only Solve Hard Problems When You Have To

When you have the option of doing something in a complicated backwards way or a really straightforward simple way - choose the simple way. This sounds really obvious, but consistently doesn’t happen. In the same way that you should rise above the internal constraints of organizations, you can rise above the desire to do simple things in complicated ways.

Sometimes a CMS just needs to edit pages - and that’s all. Maybe it doesn’t need a revision history that tracks everything anyone’s ever done to a piece of content. And even if it does, maybe you can do that in a really non-rocket-science sort of way.

The key is to solve the problem you’re solving - not the imaginary-but-complex problem that you might want to be solving.

Matt Jankowski Developer

Hound reviews Ruby and CoffeeScript code for style violations and comments on your GitHub pull requests. Free for open source repos.