This is a good thing for those people who are not aware of what is going on out there in the digital world in America. It might just shine some needed light on it. The only problem is that nobody but geeks will probably see this and the crimes of the politicians that are screwing the American people of their Privacy and other Online rights goes unnoticed until something major happens and it's far to late. A crying shame actually.
And you would know what of sexual habits you narrow minded little Winblows (l)user? It's people like you that pollute gene pools and bring down the IQ of the general public.
YOU HAVE FRIENDS!? They are really just a collection of small ants aren't they. And you named every last one of them..... you are one of those people who have too much time on your hands.. amoung other things. It's time for you go to the proverbial hell and die.:-)
You are a putz. You will always be a putz. And when you die, only your putz friends will morn you, if they can even find some way to make it to your funeral.
Mmmm more transistors means more processsing...
Lower prices means more hardware
More hardware makes geeks happy.
Happy geeks means more slashdot posts.
Good.
There are so many things wrong with this idea it's just not even funny. First off is the fact that this could just cause a more embarassing and awkward encounter in the public washrooms. Picture it, you're in there doing your business and somebody just starts talking. Are they trying to start that odd conversation with you while you're doing your thing? Or are they talking to the damn microchip in their tooth? Who knows.
Not to mention what happens if your phone rings while eating. That would be a nice sound for the other person to hear on the other end.. "chomp, chomp, chomp" And forget about the obvious sexual jokes that I am not even going to attempt to post.
The worst part about this idea is some butthead actually had to sit in a board room and go, "I got an idea" then all the other buttheads all said, "I like that, let's run with it." Personally, I would hate the idea but there has to be somebody out there that would look at it and go, "I gotta get me one o' those...."
Since no programmer is capable of producing perfect code, debugging/testing is a neccessary process. And as many people have already said, there is no such thing as too much testing. In the world of computers, testing/debugging is an always on going process. Code is only released to the public when it is determined that serious problems and/or when all of the known issues are dealt with. (Hence the nickname "undocumented feature" for bugs.)
So possibly the best and most accurate response to how much testing you should do is one that relates to how good you think your programmers and QA processes are as well as how good they think they are. You will always see bugs and problems being reported when you release a piece of software to the public. The reason is that you have a huge amount of people looking at, playing with, and testing the limits of your code. The secret to creating a good QA and code testing process is not smacking your developers every time a bug comes in (although that does relieve some stress) or changing how much testing you do without regards to processes. The secret is to find out exactly how the person found the bug and incorporate that into your testing strategies.
Also keep this little quote in mind that someone once told me, "A program is only as good/smart as the person(s) who wrote it." The reason you should keep this in mind is that programs, computers and anything else you can think of that interacts with your software was created by a human being. Thus, they are all subject to the flaws of human intelligence. Nothing and no one is perfect. It's when the imperfections mount to form a large mountain of problems that restructuring is in order.
Summation: If it isn't broke, don't fix. But tweaking is always a good idea.
Slashdot Mirror
This is a good thing for those people who are not aware of what is going on out there in the digital world in America. It might just shine some needed light on it. The only problem is that nobody but geeks will probably see this and the crimes of the politicians that are screwing the American people of their Privacy and other Online rights goes unnoticed until something major happens and it's far to late. A crying shame actually.
And you would know what of sexual habits you narrow minded little Winblows (l)user? It's people like you that pollute gene pools and bring down the IQ of the general public.
YOU HAVE FRIENDS!? They are really just a collection of small ants aren't they. And you named every last one of them..... you are one of those people who have too much time on your hands.. amoung other things. It's time for you go to the proverbial hell and die. :-)
You are a putz. You will always be a putz. And when you die, only your putz friends will morn you, if they can even find some way to make it to your funeral.
Mmmm more transistors means more processsing...
Lower prices means more hardware
More hardware makes geeks happy.
Happy geeks means more slashdot posts.
Good.
See it all works out in the end.
There are so many things wrong with this idea it's just not even funny. First off is the fact that this could just cause a more embarassing and awkward encounter in the public washrooms. Picture it, you're in there doing your business and somebody just starts talking. Are they trying to start that odd conversation with you while you're doing your thing? Or are they talking to the damn microchip in their tooth? Who knows.
Not to mention what happens if your phone rings while eating. That would be a nice sound for the other person to hear on the other end.. "chomp, chomp, chomp" And forget about the obvious sexual jokes that I am not even going to attempt to post.
The worst part about this idea is some butthead actually had to sit in a board room and go, "I got an idea" then all the other buttheads all said, "I like that, let's run with it." Personally, I would hate the idea but there has to be somebody out there that would look at it and go, "I gotta get me one o' those...."
Since no programmer is capable of producing perfect code, debugging/testing is a neccessary process. And as many people have already said, there is no such thing as too much testing. In the world of computers, testing/debugging is an always on going process. Code is only released to the public when it is determined that serious problems and/or when all of the known issues are dealt with. (Hence the nickname "undocumented feature" for bugs.)
So possibly the best and most accurate response to how much testing you should do is one that relates to how good you think your programmers and QA processes are as well as how good they think they are. You will always see bugs and problems being reported when you release a piece of software to the public. The reason is that you have a huge amount of people looking at, playing with, and testing the limits of your code. The secret to creating a good QA and code testing process is not smacking your developers every time a bug comes in (although that does relieve some stress) or changing how much testing you do without regards to processes. The secret is to find out exactly how the person found the bug and incorporate that into your testing strategies.
Also keep this little quote in mind that someone once told me, "A program is only as good/smart as the person(s) who wrote it." The reason you should keep this in mind is that programs, computers and anything else you can think of that interacts with your software was created by a human being. Thus, they are all subject to the flaws of human intelligence. Nothing and no one is perfect. It's when the imperfections mount to form a large mountain of problems that restructuring is in order.
Summation: If it isn't broke, don't fix. But tweaking is always a good idea.