This. Observe carefully the direction of the industry and apply yourself like a student to some upcoming tech. It's easier (less outlay) with software/programming but you can probably keep yourself occupied with learning admin tasks as well.

It takes a lot longer than a day to learn a new programming language. Unless you think "hello world" is sufficient.

Sync.

They killed every other option for syncing feeds/read status because they were free and very good. Now we need to scramble to create new options and get platform support.

Your interface comments are your perspective only. I loved it, it was extremely efficient.

"darn good" = "quite good", with a little bit of extra emphasis. It's a common enough slang term, where have you been?

Or, you could say accomplishing the purpose of the prefixes in creating a de facto standard. Ideally we could then simply drop the prefixes and have the same behavior. Whether each prefixed attribute behaves the same is another issue, of course.

DESQview!

Oh, wait.

I don't think that was unreasonable. If you have critical business apps running 16-bit code you need to prioritize their replacements IMMEDIATELY. That's certainly not impossible, though you will need someone skilled with both legacy and modern code.

Changing them to accommodate 64-bit OSes doesn't necessarily mean totally rewriting them, either. Maybe there are some non-compatible libraries that need to be swapped out, with a few code changes.

They would have kept one numbering system for the whole article, but "Zero-day" would have been really tough.

Apple. Or even modern versions of Windows, I guess.

For me at least, the clear advantages of a Linux desktop withered away about 4-5 years ago. Even the price of commercial OS's are almost inconsequential these days.

I have a number of O'Reilly books, and none of them have that, at least in the ePub or PDF. It is not a bad idea though.

Yeah that was a mistake. He should have said TEN average 25 year olds.

http://www.devtopics.com/programmer-productivity-the-tenfinity-factor/

You're pretty much right. Do a google search for "Visual Fred", a name given to VB.NET by MS MVPs.

...they have a Squirrel Girl movie.

It's just the next Wave of features from their Labs.

No! Especially if this is GMail we're talking about, *archive* and not delete. Delete should mean GONE (with a 7- or 30-day safety window, for example).

- I do agree with the second point. Delete if you've read it, do not need to act on it - but keep it if you thing you might possibly need to refer to it someday. Archive it.
- Avoid leaving things in your inbox. Do it, defer it, or delegate it. If you defer, set a calendar event or a todo item (that links to the email message if possible) and get it out of your inbox.

Keep your inbox like your physical mailbox. You don't leave stuff like bills in your mailbox until you are ready to take care of them, right?

Basically it boils down to: don't use your inbox as your task list! Otherwise, your process list is all backwards. Whatever comes in most recently into your inbox seems to take the highest priority, and it shouldn't be that way. Use a proper task list or calendar for stuff you need to take care of.

It is a bit of work to do this, but keeping organized is not automatic, it takes some discipline.