Remember in school you'd get the same "A" grade whether you put in a perfect 100% job or a 90% job? Sometimes coding is like this too. I work in a micro-startup (2 of us) and managed operations (read: I am coder sysadmin, etc. and tester, etc.). Given the too many things that need to be done on a daily basis, extensive testing is often just not feasible. So I shoot for 90% in my QA work and hope that it all hangs together. Most of the time that is still "good enough for government work". It's great to have teams of testers when you have resources to allocate - if I had a team to sick on this I'd do the testing in a heartbeat - but in our situation, we do what testing we can manage and move on to the next thing. If we crash (and it does happen from time to time) - we fix it quickly (grin!). One of these days we hope to be able to have more resources and I'll sing a different song. But for now we're bootstraping.
Here is a problem I'd worry about if all computers were networked together to respond in concert to an attack - wouldn't that make all those networked computers vulnerable to an attack aimed at that connected computer network?
I get hundreds of mails like this a day from all over the map. Spam laws are a good idea I think - but they won't solve anything as the problem is completely international in nature. A filtering solution or a toll-based solution (or some combo of these) is what I'm hoping for. Bring on the baysian tools because the black/white list and filters ain't cutting it any more
Slashdot Mirror
Remember in school you'd get the same "A" grade whether you put in a perfect 100% job or a 90% job? Sometimes coding is like this too. I work in a micro-startup (2 of us) and managed operations (read: I am coder sysadmin, etc. and tester, etc.). Given the too many things that need to be done on a daily basis, extensive testing is often just not feasible. So I shoot for 90% in my QA work and hope that it all hangs together. Most of the time that is still "good enough for government work". It's great to have teams of testers when you have resources to allocate - if I had a team to sick on this I'd do the testing in a heartbeat - but in our situation, we do what testing we can manage and move on to the next thing. If we crash (and it does happen from time to time) - we fix it quickly (grin!). One of these days we hope to be able to have more resources and I'll sing a different song. But for now we're bootstraping.
Here is a problem I'd worry about if all computers were networked together to respond in concert to an attack - wouldn't that make all those networked computers vulnerable to an attack aimed at that connected computer network?
I get hundreds of mails like this a day from all over the map. Spam laws are a good idea I think - but they won't solve anything as the problem is completely international in nature. A filtering solution or a toll-based solution (or some combo of these) is what I'm hoping for. Bring on the baysian tools because the black/white list and filters ain't cutting it any more