Comment Re:Weekly stack ranking! (Score 1) 424
Gah! Wrong article. So much for using a cat as a personal assistant...
Gah! Wrong article. So much for using a cat as a personal assistant...
The best part will be the weekly stack ranking and 360 degree review sessions.
"You are an A/10! Please vacate the house at once!"
Absolute not-hire. Even if the employee came to the company on their own, they couldn't extend an offer.
Correct. At one point I was told that I would have to quit my current job before I could be interviewed for a position at another of these companies. Naturally, applying for a position while newly unemployed would handicap my salary negotiating ability. The businesses viewed the anti-poaching deals as convenient for their HR operation and containing payroll costs. No pesky counter-offers...
Many tech pundits should be surprised. They were so busy writing about what a disappointment iPhone 4S was that they neglected to notice the fact that preorders sold out in one day.
...Big Deal
So you are of the opinion that it is ok to have a database; whose existence appears to be a mystery to about 90% of the public; that keeps detailed location data for an indefinite period of time (ref: years); that is unencrypted; that can be accessed not only by thieves, but Law Enforcement as well; that can be used to provide a detailed time-line map of where you have been; is not a big deal?
Ah, you should probably be aware that the phone company does this already for all cell phones. The database can be queries by any 'authenticated agent', a person with an account and password, such as a law enforcement officer. Social engineering works well, too. The US Justice Department classifies this information as 'routine business documents', not requiring a warrant.
If you don't want your location history known to others. do not carry a cell phone.
Ah, it's articles like this that make me so glad I'm retired!
C++ programmers have it too easy. Why, in C we had to code our own bugs. C++ programmers just inherit them!
Ah, I remember looking at the sorting algorithm in a low level graphics library. Tightly hand coded, packed to keep every pipeline stage filled and make optimal use of all the parallel units in a VLIW graphics processor, it was probably the most efficient bubble sort I'd ever seen.
I coded up a quicksort to about the same degree of tightness in a couple days, and, golly gee, a whole bunch of code suddenly got faster. Some MUCH faster... That was Lesson 1 for me. Optimize algorithms before optimizing implementations.
Not
Where there's a will, there's a relative.