> On purpose - probably yes. Sinister plan - rather not.

I'd argue that forcing every PC buyer to beta test your ambitious experiments is a sinister plan.

At first, I thought it was just a silly conspiracy theory that they released an intentionally crappy OS every other cycle, but I'm really starting to think they do it on purpose:

1) Release good OS with an expected lifespan of around 4 years

2) At 2 years release crappy OS. The people that bought the OS at 1) are not going to upgrade. All of the people purchasing new computers have no choice but to buy crap. While OS sales take a dip, it's not unmanageable.

3) Release good OS. People from 1) now upgrade, and people from 2) are desperate to get off the turd they bought. Money now pours in.

4) See 2.

Chrome has really good debugging tools built in. I don't particularly care for FireBug, nor do I want to deal with updating it when Firefox updates. Maybe it updates itself now, I don't know. I stopped using Firefox out of annoyance at having to deal with updates.

Chrome works, and the built-in debugging tools are pretty solid.

Sure, Chrome is recording every drunken conversation I have with X-girlfriends, but nowadays that's expected behavior.

I am not in your specific field, but close. I am 36. My advice:

Stay hungry. Keep reading programming blogs. Work on hobby projects on weekends to keep your skills sharp. Write stupid games in languages you never use at work. Obsess over every little mistake in your code. Post ridiculous nuances of horrible PHP (fill in your language here) behavior.

When necessary, stay up till 4 AM writing code. Build a team of hungry programmers. Build a team of guys who code all day, and go home and code a little more when they're not playing Diablo or whatnot.

I hate to be an anus-hole, but your post sounds like the words of a tired burnt-out programmer. I wouldn't hire you. Medicare? Job Security and Office Politics? I didn't see anything in your post to indicate that you're still passionate about software development...And passion, IMHO, is the crux of staying employable in this field.

Note: The firstname/lastname structure existed 3 years before I was even at the company. How's that for business realities?

I disagree. A LOT of programmers don't work for software shops. Non software-shop employers don't care about whether your code is elegant, or architecturally sound, or following best practices etc.

You can be arrogant and tell people to get new jobs all you want, the reality is that there is a lot of money to be made writing software for random widget manufacturer -- and they don't give a crap how you make their business thrive as long as you do.

I have been maintaining the same code base for over 10 years.

At 3PM today I was kind of down. All of the things on my plate were way too big to do before 5. I figured I'd look for simple things in the Issue Tracker to work on.

"Add a nickname field, and migrate first names with (nickname) information into nickname field."

I could do that in 2 hours...But unfortunately...

About 30% of the field guys at my company are known by their nickname. Every payroll stub, every invoice, every bit of info currently concatenates first and last names. There are probably over 300 (being conservative) places in the code that concatenate first and last name. And even if I added the nickname to this concatenation, I'd have to make sure that the SQL queries pulled this field (SELECT * is evil)

And abandoning nicknames? HAHAHA, no freaking way. There would be a company-wide revolt. Even our clients would complain that they didn't know who "Jimmy Johnson" was, ("Ohhh...Jimmy 'Big-Dog' Johnson!")

So a 1 hour task turns into two weeks. And this is one of 138 things on my to-do list.

So, how do we maintain a passion for programming?

In my opinion, you just have to sneak in every ounce of innovation. You can spend the rest of your life fixing crap that they forced you to hack in the first place. You just have to sneak in the fun stuff.

From the perspective of the average user, a fax machine is not bad technology. They buy it, plug in two wires, type a number and go.

If they are going to do the same thing with a PC, they have to buy a PC, buy a scanner, make sure they have the appropriate scanning software, make sure they're scanning the a file format the recipient expects, ensure their PC has an Internet connection, make sure the attachment isn't too large to email, get the recipient to read out their email address in the phonetic alphabet to ensure they get it right, and I'm leaving out about 20 or so other things.

I dislike the arrogant tone of this post. Just because a technology is superior on technical merit does not mean that it necessarily gets the job done for the average Joe. You try talking users through all of the complexities of scanning, document management etc. You'll buy a fax machine in two days.

I have been coming to Slashdot for a looong time. In the "old days," something like this wouldn't have been considered remotely relevant to the site. And if somebody actually posted it, 80% of the comments would be complaining that it shouldn't have been green-lit.

Now? Posts like this look just like every other political pissing-match forum. There is a reason I don't go to Reddit.

Grapes are Sour.

I quit college because of math. I had taken a ton of CS courses, almost enough to graduate, yet still had year upon year of math to go.

I have been writing software for a living now for about 16 years. I don't recall EVER using any mathematics beyond arithmetic. (Even when I was writing 3D software, the freaking API handled the math for me)

CS is taught by math a-holes because that's the closest thing that existed in academia when these new-fangled gadgets arrived. Now? It's a joke to even pretend that these bearded math lovers should be teaching anybody.

16 year old kids writing mods for Minecraft know more about computing than those guys.

BTW, if you're not writing a windowed app, and are only interested in the canvas, you might want to look at SDL. You didn't specify exactly what you were working on.

Soo...if you're writing a windowed "productivity" app, use QT.

If you're writing a custom-graphics heavy app like a game or maybe some sort of visualization tool, use SDL.
 

I am very leery of APIs. It takes a lot to sell me. I started using QT just before the move to QT4, and instantly fell in love. At this point, unless I'm writing a game, I won't even touch C++ without using QT.

QT is the most consistent, well-documented, and intuitive API I have ever used.