If you try to register multiple Gmail accounts from the same location (such as a public library), at some point Gmail will start to ask you for a phone number verification.
This is something I saw a few years ago in France (before GDPR), there is no reason it has changed.
I suspect it is to avoid fraudulent accounts while still letting a few mails being registered without verification for first time users in a location.
What was the last time you signed up for a Gmail account? At least in The Netherlands they've been requiring mobile phone numbers for years. Hell, I have a dummy account (Maps locks a lot of functions behind login) and I can't log in to it anymore since Google wants me to register my phone number 'for security and validation purposes'
Which was part of the supercontinent Pangea only 250mya, and yeast is probably nearly a billion years old. We’re not even talking about the same crustal surfaces. Given how yeast spreads, what’s the theory for how it was constrained to one small part of a supercontinent?
The article is just awful, and title aside is clearly talking about Saccharomyces cerevisiae, or is just full of shit. The claims of the article make perfect sense for Saccharomyces cerevisiae, which could plausibly have been traced through genetic studies to China. All yeast though? How do you get genetic info from a good sample size over hundreds of millions of years?!
>>Hey Jane, I need your input on how to prioritize my current work. Can you provide guidance on where I should focus?
>>Bug XYZ was assigned to me and it's taking longer to complete because we have a dependency on Vendor ABC completing a change to their web service. This is impacting the commitment to my team on Feature 123 because we are near the end of our sprint.
> Can you provide guidance on where I should focus?
Should be the call to action/last sentence instead of "Lemme know" (I read that as passive-aggressively asking for a follow up?
> because we have a dependency on Vendor ABC completing a change to their web service. This is impacting the commitment to my team on Feature 123 because we are near the end of our sprint.
Too many words. Saying that vendor ABC is completing a web service won't affect your CTA. Also, that last sentence is implied.
Here is how I would send it:
SUBJECT: Bug XYZ blocking sprint. Help?
BODY:
Hey, Jane. I'm assigned to bug XYZ. We're held up waiting for something from Vendor ABC; this might make us blow our sprint. Can you help me re-prioritize this?
Now, if Jane is one that prefers having everything upfront and is diligent about getting to her emails, then a longer, more detailed message makes sense. However, I usually send my emails with the intent of illiciting a follow-up response; too much information == TL;DR
"lemme know" isn't passive-agressive, it's a clear request. you've got to sandwich the information you are providing inbetween two copies of the request:
- start with the request, so the recipient knows why they are reading the main content of the email before they start
- give them all the information that you can to help them respond
- and then end with the request again so it's clear what you actually need and they don't have to scroll back up to read it.
the request shouldn't be more than a sentence, so it's not significantly adding to the length to repeat it.
don't be shy about asking for a response - the whole point of an email should be to get a response, and being clear about what you need in the response is just helping your recipient. And if you don't need a response, be clear about that too - but if you're sending email that doesn't require a response, reconsider whether you need to be sending the email.
It's not a (sufficiently) clear request because it doesn't contain your recommendation. If you're asking them to provide their opinion, provide yours as well.
That e-mail should have been written in a style where "yes" could be a sufficient answer to the "lemme know" if the supervisor agrees, and currently it's not.
Just get rid of the dialpad and let us use the keyboard to dial numbers. Google Keyboard already has a dialpad-style layout and you can choose to centre it or move it to the left or right thumbzone.
We already use the keyboard to type numbers and it works much better than a full screen dial pad.
The default case is the that the contestant's trick isn't original to them, and Penn just gives the trick's trade name or its inventor's name, obfuscated a little, and the contestant grins and waves goodbye.
When P&T actually make a guess about an original mechanism, sadly Teller either whispers it or draws it on some paper that they then dispose of in some suitably flashy way. (He's usually right of course!)
They're kind of vague on what the solution is since they don't want to give it away to the audience so they just kind of say a hint. The attempted fooler will generally understand what they are getting at and say if they are correct or not and there are some judges listening who know how it was done as well.
