I'll give you that the tooling is quite a bit better these days, but that's it. Practices are as horrid as ever. Cut-pasting from Stack Overflow seems like something every new grad knows how to do, and is everywhere. Not sure about your focus on design patterns--I'd often call their use a negative, not a positive. When faced with a problem, a good developer asks, "How can I solve this?" A bad developer asks, "I must find some named design pattern to mash this problem into."
At its core, 90% of professional programming is:
1. Plumbing: Routing data from this component to that one through this API
2. Processing: Algorithms, most which have been published for decades)
3. Formatting: Ingesting data in format A and displaying it for the user in format B.
This is true today, was true when I started, and was true 20 years before that.
At its core, 90% of professional programming is:
1. Plumbing: Routing data from this component to that one through this API
2. Processing: Algorithms, most which have been published for decades)
3. Formatting: Ingesting data in format A and displaying it for the user in format B.
This is true today, was true when I started, and was true 20 years before that.