What today's programming lacks is structure.
It used to be that you started coding every program with a paragraph of code that told the computer (and other programmers) what the program is going to do. For  Example:
Program Main.
- Perform Buy-groceries.
Exit Program.
Buy-groceries .
- Perform Get-grocery-list.
- Perform Go-to-the-store.
- Perform Get-groceries varying grocery-list-item-number from 1 by 1 until all-groceries-items-are-found.
- Perform Pay-for-Groceries.
Go-to-the-store.
- If the-store-is-walking-distance then
-- Get-The-Keys, Goto-The-Vehicle, Drive-To-The-Store
- Else
-- Walk-To-The-Store
- End If
- ...and so on
In today's programming, you have to find where a program seemingly starts. It may be in the middle of the code (and it usually is). The real heart of the program, however, is not even in the code.
The heart of windows programming is a hidden loop that processes the keyboard, mouse and other incomming events. Everything is supposed to be simpler to the programmer because he just fills in how the program will react to various stimuli. I've written these loops before and they're simple if you can see the code. If you can't see the code for the loop, EG-it's in the compiler or in a library somewhere, you have to know what the code does by reading a book.
Honestly, about the only structured code I've seen in todays programming languages is HTML (what produces this web page), but it's all top-down coding. That means, instead of performing Buy-Groceries which performs each detail, you just do each detail which is tedious and lends itself to repetitive code.
I should write a book. Today's coding techniques, with its objects, properties, events, and properties seems scattered brained at best...consider these Visual Basic code events (Form-load, Form-Paint and Form-Initialize), which one comes first. There are several ways to figure this out: read a book, debug the program or learn from co-developers. And consider this, where a VB program starts isn't even confined to a particular name, it's defined by clicking deep into Visual Studios menus...it's not simple getting started in todays languages. You have to read a book or use a wizard.
Then to add to todays programming mania the ever changing terminology
Every new release of software development tools comes with its own new terminology. Everything is close to working like the old release, but it's called something different...EG: yesterdays Project Groups are now Solutions. Considering that this is what you double click on to start coding, its an unnecessary change. It looks the same to me, that is, once I've figured out that someone, for some reason, didn't like the old name.