I'm fluent in C. I understand C statics fine. What gets me is their interaction with classes and instances and...

I'm not complaining about templates mainly because I'm keeping my fingers the hell out of them!

One function of special vocabulary is for specialists to easily communicate. But another, important, social function is as a badge of in-group membership. If you use the words correctly (from the point of view of the group) you show that you belong, and that you probably know and understand all the other explicit and implicit rules of the group. If the word use spreads too far it loses this function and the group needs to find new words and expressions instead.

You dislike "gelling". You dislike "paradigm shifts". It would probably be a fairly risk-free bet on what you think of expressions like "optics" (as in "the optics of this decision is good") and the like. You dislike these words and refuse to use them. Which signals to management people that you are not management and should not be treated as part of their in-group. "gelling" works exactly as intended, in other words.

Asking for words to not be used like this is futile. It would be like asking people to no longer care about fashion (another in-group signal) or to not form groups of like-minded people at all.

If you're too stupid to realize that nobody 100% separates fantasy from reality, then you have the typical intelligence of a slashdotter.

It's not? Interviews aren't supposed to be full of nothing but softball questions.

Only in the sense that it would take too long and they aren't required to know assembly.

Not many other countries intentionally bankrupt accident victims the way the US does.

I don't live in the US, and I agree. But, if you're found liable for an accident you will tend to pay a lot of money in any country; the accident victims likely have life or accident insurance and their insurance company will want to get reimbursed.

So good, comprehensive accident insurance is a very good idea no matter where you live. Usually we have that as part of our home insurance or other thing like that, and if you own a car you have mandatory insurance for that.

But in a case like this you may well be completely uncovered. The vehicle insurance is likely not valid for commercial traffic, and your home insurance may well not be valid either. As I said, I would never, ever get into a car like this without first being absolutely sure that the liability situation is crystal clear.

What they do need however is a license to operate a taxi, and that's determined locally, with a criminal background/medical/eyes check, and a very stringent but outdated local geography test that has been rendered completely useless by mobile applications such as Google Maps Navigation and Waze.

So require that the drivers have it, outdated or not. It's required by all commercial passenger traffic so it's not as f it discriminates against Uber after all. If they really don't like it, they're free to lobby and argue for a change to the relevant laws. Just arguing that "but we don't wanna follow the law!" gets tired really fast.

In the US, Uber covers you for up to one million dollars.

That's a pretty pathetic sum for traffic insurance. Remember, you may potentially be economically liable for several injured, permanently disabled or killed people, property damage and other costs. And again, as the one that commissions and pays for the trip, you just might find yourself shouldering part of the criminal liability too, if you didn't check that the guy you hired had a valid license for commercial traffic.

I don't know why Uber is complaining. All they need to do, after all, is to recruit drivers with a commercial license; require the vehicles to comply to commercial safety standards; and provide the needed insurance. It's not as if the deck is stacked against them - the other services they compete against all follow the same rules.

For my part as a potential user, liability is the real issue. I would never risk taking a car service where I'm not fully covered in the case of an accident. It's not just medical and other costs for myself; if the driver is not licensed you, as the one paying for the ride, may be regarded as co-responsible if your driver caused the accident in the first place. You want to risk hundreds of thousands of Euro in damages to save a few bucks on a taxi ride?

Don't get me started on Boost. It's caused me more than a little headache all by itself...like, say, trying to build a specific version against a specific version of OS X.

As I said, I learned about it by hacking on it. That's my point: you can't discover that kind of thing by hacking. With that said, got any suggestions about where I pick up what you think are the basics?

The basic complaint of the poster seems to be that in a store of hundreds upon hundreds of thousands of titles, only a very small number ever get discovered and successful. Huge numbers of very worthy apps never get a chance.

That problem can't be solved by any reasonable reorganization. We users (I use the Play store, but the same situation applies) have only so many minutes of time to spend looking for and using new stuff. However you make new apps visible to users, you're punishing apps that would have been visible otherwise. Competing for user attention time is a zero-sum game.

The Play store "people you know" ratings are surprisingly helpful. Unlike general user ratings this is not easy to game by the developers. But of course, those people may only have tested that one app because it was already more popular already.

I guess the only way to really fix it is to show each user only a random 0.1% subset of all apps. That would give every app a good chance of being seen and tried. But it would rather annoy all those people looking for irritated avians and not finding them.

Of course. I don't suggest my experience is typical. But I hear the same thing from other places. My wife is a freelancer, so we have a fax machine at home, but again, it is almost never used any longer. She only has it in case some client still want to use it over email. I suspect - and this is of course just my own supposition, nothing else - that people now buy fax machines only to be covered for the rare case of doing business with a technical laggard, not as a daily office tool.

Right. Before they wrote compilers, the concept was considered possibly a hard AI problem. Now they have you write a compiler as an undergrad.

I learned C++ the hard way: by hacking on a million-LOC program. It's taught me to loathe the language. It's big, complex, and incomprehensible. I once spent three days chasing a bug through a twisty little maze of templates, all different. I routinely struggle with the implications of static vs. not, member variables vs. globals vs. statics, functions that are part of a class vs. those that aren't... Getting code to even compile is often an exercise in trying something, running the build process, then trying something else, lather, rinse, repeat. It's left me frustrated enough to want to drive to College Station and scream at the walls.

All of this has left me wishing for the days of C, in which I'm quite fluent.

Nevertheless, the world seems (perhaps overly) enamored of C++, and I'm probably going to have to deal with it. How do I learn to at least tolerate it, if not like it, instead of actively hating it?

Stamping documents is seen as a way to say "I have checked this" or "I endorse this", and because you can't stamp an email or text message they print, stamp and fax documents.

I'm working in Japan, and while I almost never get or send a fax any more (it must be years now), it's decently common to send and receive PDF scans over email. In fact, sometimes you need to print out the scan, add your stamp, re-scan and send it back. I do - want to print a reference copy for myself anyhow - but I suspect some people simply add their stamp graphic to the document directly.