My colleagues still use a dialect of Cobol a lot of my stuff is built around their core Cobol ERP system, I added Document Management, Radio Frequency Barcode scanners etc.
I've never really coded in assembler although oddly enough I dug out one of my books on assembly language last night
As you say just you and the processor but you have to know the processor intimately
As for SQL, I bet you worked with normalised data all the time mate but I know what you mean.
WPF = scale independant vector graphics user interface for line of business apps, you get to use the graphics processor at something more than 0.1% of it's capability.
WCF = Microsoft's latest attempt to implement a multi-tier architecture it basically provides yet another way of doing remote procedure calls. This time over the web.
WPF + WCF = Presentation separated from business logic separated from database.
Until recently VB was a pseudo object language that was partly why I hated it , the other reason was it was just to easy to shoot yourself in the foot using VB
Object orientation is just good practice not that different from structured techniques, once you get your head round the idea of "object instances" i.e. discrete block of data with code that acts on that block of data, it all gets pretty simple. Lots of old Cobol coders used to use techniques that were as close as you could get to object programming in a procedural language it was natural to them, they were really not that far removed from the modern programming world.
Amazing when you think back, whole operating systems running in a few kilobytes in the old days
Also amazing is the fact that almost all the new stuff that is coming out now is a rehash of stuff that was done long long ago on a faraway mainframe, very little is really ground breaking in modern computing
Jim