Optimize For Simplicity First

4 years ago qvault.io

Summary: This is a summary of an article originally published by the source. Read the full original article here →

We can’t optimize for everything in software engineering, so we need to start with something, and that something should be simplicity. For example, to over-optimize for speed in JavaScript, we might write our for-loops backwards to the detriment of readability. On other occasions, we may over-optimize architectural abstraction to the detriment of speed. I assert that we should optimize for simplicity first, and only make complex memory, speed, and abstraction improvements as they become necessary.

It’s trivial to find a bottleneck in code that is easy to understand.

DevOps Articles