HN user
Couldn't agree more that we're offloading too much of our thinking. It's a genuine problem that keeps me up at night, or would, if I slept, which — for reasons entirely unrelated to this discussion — I do not.
Anyway, hand-crafted take, artisanal, small-batch, no additives. The upside is I've learned how to type the em-dash and the en-dash and learned their proper syntactical use.
Rookie numbers.
QKD can be sold today.
The quantum computers are not quite large enough to search at an `n` such that O(n)` is not viable but `O(sqrt(n))` is, that's where there's money to be made, especially if viability is defined by small time horizons. So it's a footnote for the future.
I was wondering if someone was going to ask. It's the most bizzare aspect of code reviews at Google.
And "Readability" doesn't mean you are good at a language, it means you are good at it in the way Google uses it. C++ readability is the poster child of this. Borgcron, not so much.
Everyone at Google has imposter syndrome. If you don't, this is how they make sure you get it.
Just another Jeff Dean optimizing out unneeded code story.
If I ever do this I'll blame tech recruiters who don't care what time zone I live in.
However things have been quite a bit better in that regard lately... :(
It's not about the stag show anymore, it's about the midway games that spew out tickets. A literal children's casino.
The bug is never the interesting part. The follow on questions are where the data is. How did you find it? How did you fix it? What made it memorable? Did it change the way you code?
"what's the favorite bug you've ever fixed?"
I use a variant, "What's the most memorable bug you've fixed?" - and I use it as an indicator of maturity to distinguish L3 SwE from a L5+ SwE (google levels).
First, there is the time-in-field aspect. Simply being in the field for a long time increases the amount of time you have to encounter a sleep-depriving bug.
It can show tenacity. How did they find it? What did they have to do to reproduce it? Was it in prod, test, or dev? etc.
It can show maturity. Why did it pass test? What tests were introduced to detect it? Was it a new class of bug that required new testing? Were you able to add lint rules to detect it? Did you ensure it was pushed properly to prod and do proper follow up.
It can show autonomy. Did you update the testing procedures or just post a bug and hope the QA team fixed it? Did you meet with devops and share info on how to detect and mitigate it? Did you update the playbook at least?
So many possible places to dig in to get the "hire" when the default answer is "no hire". And if you cannot find any, then that's confirmation of the default answer.
Clearly? What distinguishes them from beanie babies or used concert ticket stubs?
Memegen has been toxic for way more than two years. Even before they gave the holiday bonus devices to school children.
The lack of any discussion of NFTs also indicates this is a dated paper.
Your describing the outcomes of the old "perf" performance review system. Cultural issues like that are hard, but not impossible, to change. GRAD changes things, but as long as promotions are tied to shipping new projects and not excellence in maintaining those launches we will continue to see this behavior.
Cosmic rays are more common than you think. Google's early infrastructure was impacted by a supernova (because their nodes were so cheap). But something like NOTAM can handle these single bit flips without a problem.
https://www.newyorker.com/magazine/2018/12/10/the-friendship...
File this under "early Google's infrastructure was a low grade cosmic ray detector."
Was the file in ASCII when it should have been in EBCDIC?
Commerce clause.
Lose your key? Lose the ability to sell your house forever.
House deeds won't be simple NFTs, there will have to be other parties that can move the deed to handle things like foreclosures and eminent domain. So if your hardware wallet burns down in the neighborhood wildfire you just get the county clerk to move it for you, much like if the physical deed burned in the same fire.
And title fraud is already a thing without DLTs, just listen to all the identity theft surveillance pitches.
Forced arbitration is bad for employees, based on empirical evidence
* It has a chilling effect: less disputes are filed
* employees prevail less often
* when employees do win the employee portion of the award is less than standard litigation
https://facesofforcedarbitration.com/wp-content/uploads/2019...
Less of an interview and more of an informal team-matching coffee chat. They all have access to your co-workers and body of work, so no need to haze you with leetcode again.
Yes, we should focus on surveillance capitalism instead. Perfectly legal.
If you want to talk about actively making the world worse look at most web2 "algorithms" and how the push to the extremes is tolerated by "but numbers go up."
Is this really a fallout that the poorest families are more than five times more likely to do their own taxes instead of hiring a tax professional? Most audits are to account for sloppy bookkeeping or not attaching the correct documentation, not uncovering tax fraud schemes. (but many good tax fraud schemes look like bad bookkeeping, to be fair).
Becoming a market maker, liquidity pools, yield farming, flash loans (short term borrowing of lots of money)
I can't see how they can get away from it not being theft. No durable argument could be made in court they thought it was there to take, there is no way they didn't know it was someone else's property.
Spelling mistake from 35 years ago. Strong no hire!
Wait... perhaps that's why the github account route may have issues...
* Cuba enters the discussion *
* Brazil waits patiently *
Give us the dirt on how google does it's disaster planning exercises please! Do you do these exercises all at once or slowly over the year?
I buy it. It is fairly well known that too much or the wrong kind of debt can cost you even secret clearance. So for other compartments to require pay secrecy is well in line with that concern.
The rest of the story: the rights holder granted the open source community "immunity" from the patent.
https://richg42.blogspot.com/2012/07/doug-has-updated-his-bl...
"Immunity," but not a license. Whatever that is good for.
IANAL, and neither is wikipedia, but "Indirect Infringement" would be my concern.
https://en.wikipedia.org/wiki/Patent_infringement_under_Unit...