2,817 karma · joined December 16, 2014
I thought with Alexa we were still in the "in some dystopian future they're going to use that data for ads" phase. If we've moved to that already, I'd like to read about it.
The common thread of each of the examples you give above sounds like, "other people are incompetent."
Applying principle of charity and assuming they are all actually that bad, you've got to meet people where they are if you want to work effectively with them. Lots has been written on the responsibility of senior engineers in guiding and improving their teams without necessarily having a specific mandate from management to do so.
Perhaps you might also apply a bit of that charity IRL too though. Examine your perceptions and interactions critically.
There's no requirement in life that you have to make things work with any given team, anyway. The clueless and the checked out exist too. If you're surrounded by them and your not married to the org, consider other work.
I'd be surprised to hear they were selling viewing data though. A few years ago, they were making a lot of noise about how that data gave them a unique way to make decisions on what content to produce that other studios lacked. Seems like the kind of thing you'd hold close if that were the case.
When you search, it's also clear they have shadow profiles for content they don't have (e.g. before they had Monty Python and the Holy Grail, they'd autocomplete to "Things like Monty Python and the Holy Grail" pretty early in the autocomplete results). I wonder how heavily that search data is weighted in deciding how much to offer to license existing content.
Most standups I've participated in (four orgs now) have been ICs giving daily status reports for the benefit of the manager in the room. People making up silly rules to hurry through the thing (like, say, "we all have to stand for this meeting") makes more sense in that context.
Which would also be true for many other examples they might have picked, which makes it a reflection of the ecosystem, not a distortion.
It's a "subjective, primarily developer-ergonomics based" comparison. Seems like fair game to me.
"As a user, if I arrive on a booking page and the live API data shows our cached pricing data is stale, I expect the difference to be acknowledged."
Developer implements animation callout and an approximate, non-technical explanation
Cached pricing data continues to often be stale
Yes. I mean, of course it is. How is that in question even? I live in Manhattan, not the Bay Area, but the sum of my non-housing expenses are less than $4,315 (edit: your $9315 number minus my $5k lol rent) a month and I'm not exactly living that fresh-out-of-the-dorm lifestyle. Remember, this is the new grad number.
> Is that housing cost accurate?
Nope! It's high, obviously. I picked it out of thin air by picking a number we would be unwilling to pay as a two-earner household in NYC and then did a perfunctory check on Zillow to make sure there were Bay Area rentals at that price, which there are.
Yes it's "unfair" in some sense that someone earning that much money can't afford to buy property, but you're moving the goalposts. My point was that a baby Googler could certainly prosper financially, not that Bay Area housing prices were fair.
Well, it would surprise me :-)
According to levels.fyi, a new grad at Google is clearing $180k/year all-in.
Next tier, still not senior, clears $250k/year. That's more than $20k/mo pre-tax. Even at an outrageous $5k rent on a single income and with no roommates, you're still talking about $6k or so >>monthly<< surplus for living your life and saving.
Back in the day I had an interview for a business position where the interviewer's personal printer mysteriously started printing documents part way through. I'd just read "What Does Somebody Have To Do To Get A Job Around Here?" which listed that among other tactics a company might use to see how you handled distractions. I've suspected it was on purpose ever since. Even were it intentional though, it would be more of a gimmicky ploy than an adversarial thing to do.
An interviewer should be able to modulate the difficulty of a question without making you feel uncomfortable.
Also the job isn't done in a vacuum - being able to remain calm when you don't know the answer is an ability all its own. Interviewers shouldn't be creating artificially stressful situations but you've also got to be able to manage your own stress response!
What would the more ethical alternative be? To just take the deal on offer or silently move on?
I have no prior for themoscowtimes.com. When I googled for corroboration (as a non-Russian speaker) all I found was blogspam citing this article.
It gives me pause because, as reported, it seems almost comically reactionary. "We're going to make our own Chernobyl show but with CIA saboteurs because some historians don't say it didn't happen." From the article:
> Still, an attempt will be made to put an entirely different spin on those events. Russia’s NTV channel has already announced that it is shooting its own “Chernobyl” series based on the premise that the CIA sent an agent to the Chernobyl zone to carry out acts of sabotage.
Can someone with access to Russian media corroborate this or provide insight?
I suspect that people are mining data from ("paying attention to") certain posted keywords and then re-posting.
How might I disprove the null hypothesis that people are just repackaging highly voted comments? How might I convince myself that I am wrong or right? Please show your work or cite sources.
As long as we're saying how we really feel, we should +1 to move it up the ladder.
pub async fn do_stuff() {
// ...
}
// elsewhere, inside a fn
// as svnpenn points out
let result = do_stuff().await;You can configure Redis for durability. The docs[1] page for persistence has a good examination of the pros and cons.
My dad used to talk about negotiations from later in his career and I think he would have more or less agreed with the sentiment. I remember him talking about being tickled when someone would come in taking a particular tack, and you could more or less tell them "yeah, sure book x chapter y, how about we just talk?" and then everybody had a chuckle and got down to business. I'm sure it was more of a vibe he picked up than any particular incident. The idea reminds me of the Gervais Principle's[1] idea that different subgroups within an organization speak different languages to each other.
In support of reading books, I think there's a difference between being familiar with what everybody else has probably read vs working directly out of a playbook.
Edit:
The first link is the start of the blog series. The one about languages groups speak is [2].
[1]: https://www.ribbonfarm.com/2009/10/07/the-gervais-principle-...
[2]: https://www.ribbonfarm.com/2009/11/11/the-gervais-principle-...
Reading just enough of the git-scm book to get a basic mental model of staging, branches, and pushing/pulling from a single remote (aka the things new people actually probably trying to do with git) can serve you well enough. I've since worked on teams that expected WIP commits to be squashed, used multiple remote repos, etc, but the above should be all the git most of the people complaining about git actually need.
git remote add origin git@yabbadabbadoo:org/team
git checkout -b feat/my-work-branch
# do work
git add -p .
git reset HEAD accidental-file.txt
git commit -m "Add sweet feature"
git push -u origin feat/my-work-branch
git pull origin feat/my-work-branch
I feel like there are two big reasons git gets the rap it does separate from any actual interface issues:1. People tend to mess up with a tool more often when they are still getting acquainted with it. When things get hairy, people tend to just try random fixes so they can get back to work which makes the problem hairier still.
2. git might be one of the first tools someone uses that expects end users to map their mental model to it rather than trying to fit their pre-existing mental model.
Delta-v, as used in spacecraft flight dynamics is a measure of the impulse that is needed to perform a maneuver such as launch from, or landing on a planet or moon, or in-space orbital maneuver. It is a scalar that has the units of speed. >>As used in this context, it is not the same as the physical change in velocity of the vehicle<<.[1]
> IMO this counts as a kind of out-of-band arrangement because it doesn't involve using one of the normal return values to signal error.
My point is that if you're returning an algebraic data type Result that encodes Ok(val) or NotOk(_), you are using one of the normal return values, because the function always returns a Result. The whole purpose of the construct seems to me to be bringing the error case handling into band.