You know, sometimes when you just have this seemingly demanding problem, you can't seem to find a solution to. I found myself in a similar situation today. After writing a React Web app for 2 day straight, I finally was ready for deployment. Breathing in a breath of relief, I started working. The next couple of hours could arguably be described as the most frustrating of my life. I had all the ends covered, and this app, my app failed to start. I kept getting errors even after debugging. I decided to take some time off. Continued reading a book (The Malazan Book of the fallen), and came back to it. There glaring at me was the solution. A typo.

When I was working with the UN in drafting polices, after careful research aimed at solving some of the problems faced by minority groups in Africa, we often have, as our answer, basic and simple solutions. Same thing in the world of Finance where I spent over 5 years working with both individuals and corpations. Simplicity will never go out of fashion.

Functionality shouldn't always equate complexity. And that something is complex doesn't guarantee optimal work. As much as possible, while writing code, always have in mind that you're solving a problem, and it's your duty to do and most importantly present that in the simplest way possible.

UI interfaces needn't be overly complex, Backend code and infrastructure needn't be too "complex". Ensure easy readability of your work.

Applying this to Organizational problem solving too. An answer to a product problem, a growth problem, marketing, HR doesn't always have to be complex. That an answer solves a problem isn't enough. There is always a better answer, and most often the best answer is the "easiest" to implement, given available circumstances.

So take a step back while writing that application, while developing that project or while looking for that job too. Think simple, work simple. Solve, Build, Review, Resolve, Rebuild.