2,199 karma · joined September 29, 2009
I wrote Rebuilding Rails, which I think is pretty good: http://rebuilding-rails.com
Some stuff I've done: https://codefol.io https://github.com/noahgibbs https://codefol.io/portfolio
I'm not hard to Google for, if you want to.
So there's at least one other than the former Google ethicist who wrote this article.
A customer who uses services of this kind can "prove" they're anywhere in the world at a given time.
Useful for celebrity misdirection, criminal alibis and the like.
Here you go, I Googled that for you: http://inequality.stanford.edu/_media/pdf/key_issues/gender_...
Now, the study in question is cited.
I speak as a guy at the end of the technical track, on my second consecutive job of "look, you make as much as we'll pay just-a-programmer, even an architect, here."
Many managers are now convinced things are better. I never talk to anybody high-up on that track who thinks so. Of course, most companies don't have anybody high up on a technical career ladder, but are convinced it's going to be fixed any year here.
Fundamentally, as long as it's even 20% easier to get promoted as a manager, people are going to intentionally pick that track. In practice, it's usually 2x-5x easier to get promoted as a manager.
I don't think that's fixable. At some point, executives have to decide who to promote. Executives, like the rest of us, prefer people who have skills like theirs - I bias in favor of programming skills for the same reason.
But executive bias toward their own skills mean people managers get promoted.
I've never worked at Google. But I know a lot of Googlers. I don't think I'm wrong. Also, there's another comment from a Googler disagreeing with you in response to this very comment.
It's not a Google-specific problem. But it's a big one.
If so, you're not talking to your recruiters. You should find out more about what your side of this negotiation looks like to a candidate.
On the one hand, that screws up the usual "don't give a number" advice, including this advice -- there's usually not a defined salary range for a startup's catchall "we want somebody who does backend" poorly-defined job req.
On the other hand, I suspect "don't give a number" isn't the biggest mismatch happening there.
This makes sense. You have to be as good as the same quality of software engineer, do work that is less glamorous, and carry a pager.
Jobs in the $2X0 range are basically outside the range where a company will trust the normal recruiter/interview process to bring in a good candidate. You must start working your network, and you must either go to one of the big 6 you mention, or you must find a company that desperately needs somebody really senior and where you have an "in" -- somebody who knows the quality of your work and knows you're work $2X0.
It's not that hard to be worth that -- that's about two senior-ish engineers in Silicon Valley. But it's very hard to prove you're worth it. You have to know somebody and they have to know you.
You'll see a lot of advice about becoming a "thought leader" and "noncommodity." And to be fair, that helps -- I give talks, wrote a book, etc. But those things won't usually let you interview cold and get $2X0. At this point, maybe $200, barely? Beyond that, it's networking or seniority.
I can't tell you about $3X0, that's out of my personal experience.
You'll occasionally see massively outliers, up to maybe $6XX (which includes stock, not just base.) But those are almost invariably people who rose in the ranks at very profitable companies -- either big 6 or a small niche company that makes bank. It's very hard to be hired into a role like that unless you're well-known by the company in question.
Frequently people do well on the technical-not-actually-coding portions and very badly on the please-write-code portions. That is, if we didn't ask the specific coding questions, we'd be hiring people they disqualify.
At those places we less frequently hire people that just can't code -- though I've been around for that too, usually when we look at a resume and say, "oh, we don't need a coding test for him, he's been writing important code for years in a way where he couldn't hide lack of ability."
It would appear that a resume is a poor way to verify that.
More often than you'd think, alas. I'm going by about fifteen years of personal hiring experience, for whatever that's worth.
Well, that and getting multiple compilers to use the same name-mangling standards.
And LinkedIn certainly does that kind of thing (example: sponsored posts on the front page inserted between posts from people I know, formatted identically, differentiated only by a medium-gray-over-white "Sponsored.")
But glad to hear that in this case you just mean showing fewer ads to those who don't click on them.
So okay, you're already very familiar with LinkedIn's misleading dark patterns. You are, for instance, making ads look like real content in order to get people to mistakenly trust them more.
This makes your claim that you're hard at work "trying to improve the clarity of our products" mean something different than I had expected.
Sucks for you, but you're the product, not the customer.