Yeah I got the feeling they were trying to use SJW language, in order to blockade it being used against them.

It's easy to get something to negotiate with: apply for a number of jobs, and compare the salaries they offer you. If the job you particularly wanted didn't match the salary offer from another company that you didn't want so much, you could ask the company you wanted to work for to match it.

I've always thought the critical flaw of Extreme Programming is that most programmers are introverts, and tire of being in another person's company. I know I think best when sitting quietly on my own.

I originally preferred upper case, cause capital letters look more like numbers, so the number looked more consistent.

But then I found that everyone used lower case (in C++ code), so I gave up and switched to lower case.

The question didn't ask specifically about void as a return type though, but rather about all general usages of void. There is lots of 'void *' action in C that's replaced in C++, and that's what bioemerl is referring (correctly) to.

Void is more of a C feature than a C++ feature. Chances are, if you find some code that uses void, it could be better written with C++ features such as templating, overloading, etc. It's mostly included in C++ for backwards compatibility with C.

Edit: As others have pointed out, this is apart from its usage as a return type from a function, where it means 'this function doesn't return anything'.

Nah, it's 'percentage of peak'. All Google Trends graphs show the highest point as 100.

I usually see this kind of error referred to as an 'array overrun' rather than the more generic 'memory stomp'.

Yeah there haven't been any articles, until a big spate of them recently, all based on the Github 'study'. The same Github that's embroiled in a divisive controversy about diversity just before it published that study.