Hardly surprising - staff in many mobile phone shops are woefully lacking in even basic knowledge. My mother was recently told by the "salesperson" in carphone warehouse that there was no way for to keep her number when changing networks. I was gobsmacked.

shenanigans!

"the Go program ran slightly faster – though the C++ program was slightly shorter and easier to write because the C++ code uses automatic deletes and allocation instead of a cache."

So in fact the same set of optimisations were not applied to both the Go and C++ code, since memory caching is clearly an optimisation.

and yet...

they don't seem to be able to use this for something useful like issuing me with a residents parking permit without me having to provide a mountain of documentation.

*yawn*

"If you're a Google Apps user and you've enabled beta programs".

beta software in 'has bugs' shocker.

meanwhile in the real world...

'We strongly suggest that you use different passwords for each service you sign up for'

Oh yes good practical advise. If I did this then I'd quickly have to start writing them down to remember them all. I mean I'm probably using up to about 10 different variants of user credentials across everything at the moment and I that still means a hell of a lot of duplication.

So which is the more cardinal security sin? Duplicating or documenting?