They also did the soundtrack to the movie "Legend."

I'm glad you are not. However, in my experience, you are the minority.

1st Job: Retail IT: 1.5 years - My Manager was actively committing fraud. The Store, District, and Regional Managers didn't care because he wasn't defrauding the company but instead our vendors and it made their bottom lines look good. A head hunter shopped my resume to a potential employer without my knowledge. When they called to followup references the got my manager. In spite of my being on contract, with 5 months to go, my Manager lied to the Store Manager and said I had called in and quit. Imagine my surprise when when I showed up for work the next day.

2nd Job: Pseudo State Agency IT: 3 Years: - When Accounting/HR VP got in a turf war with the IT VP I became a casualty. In spite of being an A+ and MCSE Tech HR decided I did "Data Entry." This meant I would get no pay raises until my new reduced pay rate matched my current pay rate... which would take 13 years. For 9 months the IT VP did nothing while promising action only to finally said "It's not worth the political capital to correct it, you are just a tech, you are replaceable." As note I ws the first tech they had managed to hold onto for longer the 8 months... a trend that continued after my departure.

3rd Job: State Agency IT: 2 Years - Lucrative wiring contract ended up be given to my Managers Brother-in-law. After being 6 months behind schedule announces wiring job is done and I am supposed to sign off on it without testing. I refuse and follow testing protocol. 40%+ failure rate on all the wiring and discovered that even though top of the line commercial switches were paid for consumer grade switches were installed and daisy chained in an unstable configuration. My refusal to sign off on it resulted in me being censured and a poor performance evaluation.
My complaints to higher up were basically answered with "He's a manager and you are not, your opinion is irrelevant."

4th Job: University IT: 5 Years: Actually the best of the bunch. Boss was likable and work was low pressure. Boss was continuously on 1/2 time as he was taking a ton of continuing education classes. When he started talking about retirement, and I pointed out that if I was going to take over the Novell network I was going to need a different suite of certs and additional training... magically all of our training money was unavailable and continued to be unavailable for anyone but him. He also had a tantrum when I gave him 8 weeks notice that I was going back to school, basically not talking in anything monosyllable the entire time because he would actually have to do his job for the first time in 5 years.

Each of these are specific instances from each of my jobs, but I could fill pages with their self-serving behavior. Far more often I saw empire building instead of teamwork.

A serious entry to the question.

Working in Alaska we had an equipment failure at a microwave bounce station and I was the closest tech. I and a telecomm guy rode snowmobiles about 20 miles back to the site in practically balmy weather of only -10 deg f. However, the bounce station was on top of a 40 foot tower which was perched on rocky hill that rose out of the forest.
There was thermometer helpfully bolted one of the legs of the tower and it only went down to -25 f. It was colder then that.

We climbed to the top of the tower, where the wind was howling like a banshee, open the box... to discover a router that apparently had been missed when we run around upgrading all the equipment 5 years previously. One for which used proprietary embedded OS that I had no experience with. Fortunately, my boss did but she was on the other side of the state. So I jacked my serial cable in, called my boss on the radio, with my laptop randomly freezing and crashing in the cold, bitten by the Artic wind and with crappy static filled radio connection I laboriously reprogrammed the damned router frozen keystroke by keystroke. I took nearly two hours of hell to bring it back up but we did.

Gratefully we climbed down the ladder and prepared to journey home. The snowmachines wouldn't start. The details of fixing THAT is a tale for another thread.

I'm curious as to why you categorize Architecture as "bullshit" degree.

Would you mind explaining the Rationalization behind this?

I'm curious because I have 15 years in the IT industry and am now getting an M.S. in Architecture and I've never heard of someone refer to it as such.

Ethical... probably not... but he could have it MUCH worse.

I also worked a large University and the department I worked for specialized in statistical analysis. One of the major Government grant groups who we did a lot of work for switched over to a unbelievably complex and buggy contract/grant writing software and required that it and only it be used to submit grant or work requests.

One License = $6000.

And it was so laden with DRM and key-checking that if you suffered a the tiniest bit of latency at ANY step of filling out the grant forms the software locked out out and had to be reactivated by the vendor so you could start the whole grant form over again (no saving.)

It was so burdensome we had one financial manager take early retirement rather then deal with it anymore and when I left they were trying to decide which was more cost effective: hiring a person to deal full time with this one piece of software and it's eccentricities or stop bidding on those grants... losing ~20% of our grant money in the process.