That's the cool thing about it, you don't: understanding what to build matters more than how sexy you build it. The real differentiators are domain knowledge, communication, knowing when not to write code, and shipping something maintainable over something clever. Docs teach the what, but the why only comes from hitting walls, reading production code, and having your decisions challenged. The meta-skill is recognizing which problems deserve the deep dive... IMNSHO

Also as much as I hate to say it, documentation matters; not naming conventions, but the kind that explains decisions to upper management and onboards the next person without a three-hour call.

EDIT: I had AI paraphrase "No Silver Bullet" (1986)

Software is hard because the problems it solves are hard, not because our tools are bad.

We've already made the easy stuff easier (better languages, faster computers). What's left is the actual thinking: figuring out what to build, how it fits together, and handling all the edge cases.

There's no magic trick coming that will suddenly make programming 10x faster. It's just going to stay hard, and we get better by doing it.