It doesn't have to. But most software people tend to design solutions starting from "best practices" and address every imaginable problem ("what if X and Y happ

It doesn't have to. But most software people tend to design solutions starting from "best practices" and address every imaginable problem ("what if X and Y happen while Z is going on?") so they often end up with complicated stuff. Whereas, if you start from scratch and focus on the most efficient way to address only the main problems, it can be brutally simple.