Which makes sense, because the methodology used in building applications is lead by people who invest all their time into developing. Simplicity costs you power

Which makes sense, because the methodology used in building applications is lead by people who invest all their time into developing. Simplicity costs you power, and most people crave power when they spend all their time doing something. That, and meeting requirements written by people who assume they're gods. I don't find the struggle intellectually trivial at all. Over time you learn many ways to deal with it, and sometimes even get it right on the first try. Those skills can be fundamentals about computing, architectures, programs, libraries or languages. Sometimes your knowledge of tooling, methodologies or coding styles get you there. After a while you can even apply some profiling to the author(s) something you're using, because "this kinda guy probably did this", "they always do that". To me reverse engineering things, on every level, is very interesting, and part of the path to being a great (practical) engineer. Not to mention, if there were a proven stack where everything clicked easily, and stuff just implemented itself, we'd have heard about it. There are integrated platforms where anyone can get something up with ease, but if they added all the features you'll eventually miss, you'd end up with something as complex as starting from scratch!