Alternatively, nearly half the students taking the test are far enough along the autism spectrum that they could not answer the questions about implementing getter methods when faced with a class containing private member variables with no methods to set them.

On the other hand, this article (7th from the top of the May 2015 list) makes no mention of anyone by name, so it may also be possible that the victim is able to request its removal, despite not being identified in the article.

To hack the account, they need both the account number and either the PIN or password. This allows them to brute force the PIN, and retrieve the account number as a byproduct of that. Knowing the email address or home address only gets you the account number.

You mean like this?

Indeed. And my programs would run a lot quicker if pi was 4. Does anyone really want pi to be anything other than 4?

Now that his destiny has been fulfilled, Microsoft no longer needs his services.

Or maybe they do need his services again. Watch where he goes next very closely. That is the industry Microsoft wants to fail in next.

Mike Stock, Matt Aitken and Pete Waterman mostly,

Of course, administration of the pot consumes 80% of the remaining revenue after Apple's standard 30% cut, which is entirely taken from the artist's cut as "promotional expenses".

If it was Google who wrote Windows, we would have hit Windows 95 back in the 1980s.

The Google Windows 95 beta was discontinued in 1986 after too many people came to rely on it for their daily work.

The Windows key only really became a bad idea in Windows 8. Before that it was relatively harmless on its own, and quite useful as an additional modifier key.

This is clearly a conspiracy by Emacs users to make vi unusable on Windows 10.

Uh, no. Amiga's default stack size was 4 KiB (4096 bytes), and did not auto-extend. So nothing of any significant size was going on the stack.

Is anything of significant size needed to control an HVAC system?

For a full comparison, remember that US has both state and federal taxes, and that education, health, retirement and employment insurance are separate expenses that you need to account for over your life time (not just in your twenties when you are young and healthy and your parents have provided for you so far in life).

I've seen all too often in my career introduction of good new processes fail because noone is there to champion them. As a manager of an established embedded development team that is still working "the old way", I accept that I'm going to have to 'do everything for the developers' until I get their buy in. The alternative of forcing new processes on developers before they've seen the value themselves just causes them to grudgingly follow the letter of the process with the intention of making it fail. If the processes you are introducing bring real value, then the developers will slowly see this and embrace them. If the processes don't bring value, then suddenly realising 3 months later that you've increased your own workload with no benefit is the best filter. I've successfully introduced my team to 100% coverage code review this way, and am working on unit testing now.

It reduces the pool of resumes that you have to sort through into just previous employees and liars. Since you know that the previous employees are either no good or have a grudge against the company, you can filter them out and hire the rest for sales.