Is there any evidence that there was any delay at all?

Seems to me once you have the intelligence to make and use a spear, it ill only be days at most before you're gonna try throwing it, at least partly because throwing whatever you have in your hand is what you would automatically do if you've got some pissed-off large animal (such as one thats just been prodded with a pointy stick) chasing you.

>> How do you or your organization handle such people?"

At my company, they seem to get promoted.

Is there any evidence that there was any delay at all?

Seems to me once you have the intelligence to make and use a spear, it ill only be days at most before you're gonna try throwing it, at least partly because throwing whatever you have in your hand is what you would automatically do if you've got some pissed-off large animal (such as one thats just been prodded with a pointy stick) chasing you.

The government's sole purpose of this action is to put into place more mechanisms to extract new taxes. The standard way all elected governments of the world get away with sticking it to the people with more unfair laws is to play the long game and start really small.

The gov knows that once the basic mechanism is in place, it is irreversible, consequently they initally make it sound harmless and agree to anything to get it in place (even initially giving up any benefit, such as that all the collected taxes all get returned to the big companies) because the gov know they can gradually tweak the new mechanism's parameters later when the spotlight isn't on them. This is government tactics 101, people.

Why would he be saying this now?
I'm guessing this is a clear sign that Google are heading off into doing something with sharing medical records next.

Most of the posts here are making arguments and suggesting actions that were exactly the same as the ones that generated loud complaints on Slashdot when it was about Microsoft using proprietary crap to lock out Linux/Open Source.

I don't like Microsoft at all, but supporting Google acting more like them is no answer either.

Are their releases really called CPUs?
If so, that is so amazingly stupid it appears actually designed to confuse.

If anyone can print a cannon, Cannon can.

That alone doesnt see to be even sightly effective enough.

We should also control access to grinding wheels, coz you know, they can be used to make knives that hurt people.
We should also control ownership of screwdrivers and all other tools, because they can be used to make WMDs that are used by terrorists.

I think you mean "Case in point", and I think you have cause and effect backwards.

Its not that they are fast programmers who happen to somehow also write good code when given a limited time; rather Its exactly because they take the time up front to write robust code that they can get games out fast with minimal bugs, due to the subsequent lack of hidden extra time costs that most managers dont understand so never account for, such as subsequent rework needed.

>> If you are smart enough to win such competitions, you are likely a quick study who can learn new skills rapidly.

But I would also guess, way more likely to be an arrogant dick who doesn't play well with others. Most business do not want 'stars', they just want compliant code monkeys that simply follow orders.

>> Don't you think a programmer who can churn out working code in a short span can do "properly engineered code" when the need arises?

Possibly but not usually, as it tends to be a polar opposite mindset.

Yeah you just exactly demonstrated the point I was badly trying to make, that not enough people emphasise or even realise how productive doing a thorough job is, rather than doing a superfcial one.

....all those competitions do is find the fastest programmers.

Fast usually means hacky. it definitely does not equal good, but unfortunately many managers dont understand that concept because they all subscribe to the "make it fit in my microsoft project plan" mindset.

Sadly, In this culture, poorly engineered and buggy software and the corresponding very costly rework have just become accepted as unavoidable even though its actually not.

Its actually much cheaper in real (but unfortunately largely hidden) costs to take the time to get it right before you deliver to the customer.

I'll take the programmer who loses these competitions because they took the time to do a robust job thanks.