You may add feet for altitude (you fly in levels that are in hundreds of feet, like FL300 is 30000'. In meters you get to fly separations of 300m which can be much more error prone).
I've flown to Moscow dozens of times and the altitude in meters is much more confusing(even if you only use it now below the transition level, from 0 to 3000'), the wind speed in m/s you may get used to, but Knots is much better for all speed units (also the mach num aproximately corresponds with NM/min, example 0.80 Mach is 8 NM/min.)
Counter offers are a little silly. People in our industry are already making far above the median, which makes it extremely unlikely that money is the motivation behind resignation. More often it's a bad manager—there's a saying that people don't quit jobs; they quit bosses—uninteresting work, change in direction, or some other environmental factor. If you're going to make someone a counter-offer you should also be sure to address the real issue that caused them to want to leave in the first place, or they're just going to leave after a short time anyway.
Yes, by all means, ask for what you're worth. My point is that money is almost never the reason people decide to start looking for work elsewhere. A counter offer by itself is sort of an empty gesture that is bound to be ineffective in the long run as a retention tool.
The median income in the US (in 2014) was $29k. The median salary for a software engineer is supposedly $95k. That's more than triple the overall median.
That's the average salary for a software engineer, not the median. Also, the SSA site uses "net compensation" for their numbers, which they define as "compensation (wages, tips, and the like) subject to Federal income taxes, as reported by employers on Form W-2" and "includes contributions to deferred compensation plans, but excludes certain distributions from plans where the distributions are included in the reported compensation subject to income taxes". It is not clear to me how that maps to salaries reported on Glassdoor.
I didn't redefine anything. I pointed out that the "median wage of all wages" does not add anything in the discussion when we're talking about skilled labor. Trying to compare skilled labor wages to all labor wages of course is going to make it seem like the skilled labor is getting paid too much. That's what's dishonest.
It is all about point of reference, depends on you are comparing yourself with someone that makes you more in industry or someone that makes less in other industry.
When I was there I was taken into the VAB with a group. The SRBs for the next Shuttle launch were there. Nobody else was in there. "Security" consisted of a guy asking if I had any lighters or matches.
FWIW the Unicode spec describes combining marks as characters in their own right. So if the intent is to reverse characters, page 21 does the job. The resulting sequences will potentially be defective but not ill-formed.
That being said, an FAQ on combining characters points out that Unicode's definition of "character" may not match an end user's, and that it's best to use the word "grapheme" instead for clarity. (And that being said, if the typical end user knows what "grapheme" means, I'll eat my cat.)
So from a practical standpoint, it's best to make sure that any input to rev is in one of the composed normal forms.
(Incidentally, the proper sequence is <base character><combining character>…, not the other way around.)
> Incidentally, the proper sequence is <base character><combining character>…, not the other way around.
A mistake in Unicode, IMHO. The other way around, it would have been possible to identify the end of a combining sequence without looking past the sequence. Also, ‘dead keys’ could have directly generated the required combining characters just like normal characters, rather than requiring special processing.
