Glory in software engineering??? Excuse me if I disagree, having been a software engineer, programmer, systems analyst, DBA, consultant and technical director in my career.
The glory of IT is not in IT, but in software engineering. IT is the dark, smelly, hairy underbelly of computing technology. Software engineering is the light, bright, wonderful topside, basking in sunshine and wonder.
Software engineers are given the challenge of a problem to solve, and the money and time to do it in. Good software engineering consists of designing the most elegant technical architecture to solve the problem.
--- Uhh actually software engineers usually are required to work extra hours because there is not enough time in the budget. Add onto that almost every client, whether inside the company or an external company "balks" that the time estimates are too long - so unrealistic estimates are usually put into the project. As for "most elegant technical architecture?" Only in the top software companies will you see that. In most places - whatever is good enough is used.
Software engineers regularly meet with executives in fancy boardrooms with glass tables. They are there to design quality solutions that will be used by thousands or millions. They are treated with accord, respect, and often, mild deference. Lunch is often provided by hired caterers at design meetings.
--- Uhh, actually most of the executives are scared to death of Software engineers and rarely talk to them. Usually, there are about 4-5 levels of team leads, project managers, directors, etc before you even get to the executive level. Catered lunch is only given to SAP consultants, and that was in the past. As for respect - actually we are typically screamed at when something goes into production that fails - even though it was the QA teams fault for not testing it enough.
There are never enough qualified software engineers - they are pretty much always in high demand and paid to match. When software engineers work in a field, they quickly acquire domain expertise that's almost impossible to replace.
--- Uhh, actually many of us made more money in the late nineties then we do now. Because rather than having good, high quality software, many firms choose to outsource the development - so we spend most of our time fixing bad code that was written overseas. As for domain expertise, some of that is true, but the language and platform "dejour" changes so fast that someone that is a irreplaceable expert today can be a nobody tomorrow. Did you ever hear of "PowerBuilder" for instance? I bet those guys are really in demand these days - NOT.
People who confuse IT and Software Engineering often wind up working in the wrong field. Put in the time to become a software engineer, and you won't ever regret it. Cram through your MCSE or CCNA, and become one of the faceless droids. (Yay! I know what an MSI file is! I can calculate a subnet!)
So instead of being an IT slave, I can be a Software Engineering indentured servant? Come on man didn't you ever watch "Office Space"??? Those guys were software engineers, not IT staff. In any case I sincerely hope you were being sarcastic about software engineering. Otherwise, either that was a really good joint you smoked before writing this or you have never actually been a software engineer in your life.