Scrolling through a thousand others' code on GitHub, is not what a cabinet maker does.
You want a standard for all programs you could build, put it in the CS degree or a 1 week training course that gives you a license at the end. Like a forklift guy goes through and happens to come out the other side knowing all the basic rules. The forklift guy doesn't have to scroll through thousands of GitHub projects to infer from studying, what could be taught in a week with some decent management and/or training.
When there's no standard, literally of course everybody's a beautiful snowflake who comes to their own conclusions. We have trained people to be that.
Of all the suggestions I could make why not cut to the deepest one. We're not going to have standard programming patterns understood by your average-joe-coder fresh out of university, until those patterns have been integrated into the English language like Greek drug terms and Latin legal terms.
You can learn and build a entity component system for a video game in a week, come back after a month of exciting holidays later, and discover you've forgotten what an ECS even is. But the biological concept of evolution (or contract law, or anything else) is learnt-once and stays with you forever.
It's time that the basic programming concepts have fixed names that don't change. That are embedded in the English language, taught at school from grade 0 and are distinguished from normal English words with some ancient-yet-familiar dialect. Ancient Americana if it were possible.
I'll make a standard. The next generation of children won't even realize they already know "how to program" by the time they are 9 years old, and they won't argue about the existence of these concepts, nor forget them, they'd just argue the style of them. We'd skip generic English words like "game loop" and acronyms like "ECS" and have real identifiable phrases in a familiar-but-old language that refer to powerful concepts.
/soapbox