I just spent 15 minutes Googling this guy because his site in his profile was interesting. He humblebrags about employability, but he's incapable of finding work. He also makes bomb threats: http://blog.up.co/2012/04/30/not-even-bmob-threats-could-det...
From time to time I toy with the idea of suing that joker for libel, but the reason I don't is that I support the notion that the best response to hate speech is more speech.
I think newer versions of C++ are going in the direction of Haskell: a lot of additions that make functional programming much more pleasant to use such as lambdas, variable templates, etc, but I couldn't remember any new C++ feature designed for traditional object-oriented programming. So to me it's entirely understandable that object-oriented aficionados would find C++ less and less likeable.
Better OOP is definitely not the direction the language is going. C++11 added override and final. C++14 had no OO features. C++17 may get UFCS (i.e. f(x, y) == x.f(y)), which is either an OO feature or another step away from OOP depending on how you view it.
Liberals tend to favor equality of outcome while conservatives tend to favor equality of opportunity.
These kinds of diversity reports usually show that "white people are overrepresented" and "hispanic and black people are underrepresented". They usually do not mention that asians are GROSSLY overrepresented. It doesn't fit the agenda because, despite being the most successful ethnic group in the US in terms of income, they are not considered "powerful".
I ported a project to Rust and then ported it to C++14 (which is awesome!), but I only did that because Rust was in a state of massive flux at the time and I got tired of the project breaking every two days due to changes to the compiler/syntax/stdlib. I plan to reevaluate Rust once it's settled down a bit.
Sounds like a pretty successful bidirectional filter to me. (As in: you apparently don't want engineers who don't know this detail, and I wouldn't want to work at a company where that kind of trivia is a litmus test.)
It's not trivia. If someone doesn't know the difference, they're going to allow bad data into our database. Large webapps with poor model validations are security and maintenance nightmare.
Actually, I am reminded of an error that happened which was similar to this. After I left a past company, an engineer flubbed a validation which allowed a subtle bug to go undetected for 10 days which cost the company $500,000.
No, money wasn't being stolen, but the validation error meant that clients' money was being spent and not being tracked. The company had to eat the costs.
