Sometimes the Simplest Solutions are the Best Solutions

DZone 's Guide to

Sometimes the Simplest Solutions are the Best Solutions

Stuck with an enormous problem you can't code your way out of? Take a step back and take a simpler approach to code design.

· Agile Zone ·
Free Resource

How many times have you seen or written code like this (in any language):

    someFlag = false;
    someFlag = true;

I’ve written code myself like this many times, and seen it in many places too. Usually for toggling display of some content: “if it’s hidden, show it; otherwise, hide it”.

Recently I’ve been spending a lot of time learning and coding an app using AngularJS and I keep seeing this pattern repeatedly in many code examples:

someFlag = !someFlag;

When I first saw a statement like this it took me a couple of seconds to understand the purpose, but then when it clicked I laughed out loud in one of those ‘ahah!’ moments, as the outcome of this code is exactly the same as the code above.

When we translate design to code, sometimes thinking in logical, procedural steps hurts the ability to translate to code that best uses the features of the language or platform that you are running on. Sometimes the simplest solutions really are the best solutions, although maybe it takes a different thought process to get there.

agile, design patterns, languages, productivity

Published at DZone with permission of Kevin Hooke , DZone MVB. See the original article here.

Opinions expressed by DZone contributors are their own.

{{ parent.title || parent.header.title}}

{{ parent.tldr }}

{{ parent.urlSource.name }}