Um.. I'm pretty sure we already have these... and that millions of people use them on a regular basis, and have done so for a fair few decades now. I myself will be utilizing a flying carriage traveling from Houston to New York tomorrow morning.

The exact same way you make any transmitted information (such as a text password) secure. There is exactly zero fundamental difference between the problem sets. You still have to prevent eavesdropping at all the various levels at which it occurs, and you still have to choose the information in such a way that it is not easily guessable or deducible (don't choose a family member's birthday or anywhere around your house).

The headline for this article is not clever. It is unclear. Unclear is not the same as clever.

I can not, for the life of me, figure out why anyone would have "Thought that 2009 was the year botnets died". Really?

Thought that 2009 was the year cancer was cured? Well think again! .. wtf?

Obviously, you have never heard of Socratic Questioning. Enlighten yourself. Start here.

By degree I am a Computer Scientist, and I also emphatically agree with everything you have said, particularly your handyman analogy.

Part of the problem, which causes me no end of grief, is that when most people go to school to become "Computer Scientists", they are really trying to become handymen. Most universities do not do a particularly good job of discouraging this notion, partially due to economics, and partially due to the fact that there is no distinct classification for "code handyman".

I recently interviewed someone with a Computer Science degree from a very respectable private university who could not even attempt an explanation of what NP-Complete meant. Because of the university in question I feel sure beyond doubt that he must have been exposed to and tested on this information, yet it was blatantly obvious that this person was more concerned with whether or not he could say he "knew Java", or some such. When this person went on to say that he felt that the university had not adequately prepared him for the job market, my head nearly exploded! (and not just because this is a stupid thing to say in an interview). Admittedly, this is an extreme case of this sort of mentality, but I have observed that milder cases seem to predominate the industry known as "Software Engineering".

To make matters worse, the majority of programmers I know are not even familiar with the idea that something can be formally verified as correct, and they will even go so far as to reject the notion that there is such a thing as "correct"!! They will say something to the effect of, "how can you tell if something is correct when there are a thousand different ways to accomplish the goal", as if a plurality of solutions implies that there are no wrong ones.

It is as if all of the mathematics generally required for such a degree mean nothing.

My job title is Senior Software Engineer. However, when people ask what I do I try to give them an accurate descriptive answer of what I actually spend my day doing that I think is most meaningful to them. Depending on the audience, this usually turns out to be "Computer Scientist", or sometimes even "Mathematician" (especially if I think they are going to ask me to fix their computer).

Please describe the physical relationship between "human" and "land" that implies "ownership". If your description has anything to do with who is standing on it and/or using it, then your first statement is bullshit.

Yes. Actual Information Technology. It has been my experience that the projects that have been successfully outsourced are projects that involve zero new technology and have traditionally been implemented by considerably overpaid "engineers" who can't tell the difference between a Turing Machine and a vending machine.

In my opinion, 2/3'rds of the software engineers I have ever met deserve to loose their jobs for the simple reason that the resources they consume are more valuable than their net production, usually by a staggering margin. It is as simple as that.

Yes, my job title is "Sr. Software Engineer". No, I will not tow the union line.