Slashdot videos: Now with more Slashdot!
We've improved Slashdot's video section; now you can view our video interviews, product close-ups and site visits with all the usual Slashdot options to comment, share, etc. No more walled garden! It's a work in progress -- we hope you'll check it out (Learn more about the recent updates).
however that will provide the average prankster endless fun rerouting you or causing jams
- if some cars are manually driven, you will be able to drive them in such a way that makes an automatic car misbehave (stop) ignoring the safety bit here
So this is the last Groklaw article. I won't turn on comments. Thank you for all you've done. I will never forget you and our work together. I hope you'll remember me too. I'm sorry I can't overcome these feelings, but I yam what I yam, and I tried, but I can't.
This is in response to the ongoing Snowden debacle. Please go to groklaw and read the full article. Her response to the 'if you have nothing to hide...' argument is ' I don't like uninvited strangers looking through my stuff' and that not being watched is a key human freedom.
I would add, if you are a us taxpayer, you are paying for this. A sad day."
Link to Original Source
one by front door / hall table to wifi on
carried out by throwing dice / abacus / mental arithmetic
morons / normal people / genii
If the process was not validated and the results were not checked, why is anyone surprised when it is wrong?
Some areas can be defined as right or wrong by people with good minds and strong opinions - games
Tax and Financial software not so.
At some point in the process $product needs to be validated using $external_process by $people_who_should_know
I am betting this did not happen.
basically it should be clear to all that if you design,code,test,doc,release,stop - that is the most efficient approach. say this takes an effort size 1
the trouble is that what is released is probably not what is wanted.
under agile effectively you take a small part of the job and design,code,test,doc,release,stop let the customer loose and then repeat.
repeating this process n times for each 1/n th of the project takes more than effort size 1 as even if you never even look at any part of the code previously written, the tests you are adding and running will - and the whole point of agile is that you iterate toward the true requirement so you will be re-working.
the trouble is that what is released at the end will cost more.
please flame me for stating the obvious, but if you know what you are doing, and what is needed you should use something like waterfall and if you do not know what you are doing/is needed, use agile
Link to Original Source