back when it was win 95 or NT, the was no large established ecosystem that relied on a API and any changes to the UI were clearly better. 20 years later there are billions of users all dreading the thought of something different - and win 7 counts as different. there are hundreds of thousands of developers all thinking the same. your customers don't want change - but you only make money if you change. the only thing stopping MS becoming altavista is that MS enables so many critical businesses processes using VBA and until processes change, that won't change.

actually, in the UK, the pensions regulator has very extensive powers to do just about anything that protects the pension fund. this includes preventing mergers, going after foreign parent companies after they have sold the subsidiary, and the directors. sounds draconian but it is there to protect your 80 yo grannies pension - otherwise you would have to look after her

- they will be networked, this will make them safer in normal use and you should get there faster
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

one in wallet / car to turn wifi off
one by front door / hall table to wifi on

The calculation could have been done on paper / blood on a wall / notches on a stick
and
carried out by throwing dice / abacus / mental arithmetic
by
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.

mod this as funny better yet sarcasm

hour of the pig quite good v funny

This is the same sort of discussion you get with c++ vs php - the question is what is the job.
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

Q: a tool optimized for client server crud applications A: powerbuilder

3+3+3 = 9

someone called fishburne posting about gambas what are the chances of that? could be a variable from the poission distribution