What problem are you trying to solve?
Too many products are a solution searching for a problem. People jump into the building phase instead of questioning if there is a need for their product, they waste hours building something useless. The best example is the $699 fruit and vegetable juicer Juicero that makes juice from pouches you can squeeze yourself.
Software Engineering is no exception to this hyperactivity. Many engineers write code without understanding the problem they are trying to solve. When doing so, they add unnecessary layers of complexity. It makes the system harder to maintain and operate. And add potential issues you didn’t have in the first place.
Before you start working on a product or writing a single line of code, ask yourself what problem you are trying to solve. Question if this problem is worth solving. Only then, start working on the solution and focus on this problem only.
Go incrementally, one problem at a time.
You will be amazed how following such a basic principle helps you cut through the noise, solve real issues and improve your bottom line.