skysight-inc/HackerNews huggingface dataset:
I had 4 onsite interviews in 5 days once. It was brutal, so exhausting. I felt like a machine though. A lot of the questions were recycled (behavioral), and so were some of the tech questions.

I don’t know how they managed to do 6 in 6 days, that’s almost hard to believe. Most companies aren’t so flexible on the days they can host you.

It would have been very interesting to see how the offers compared and which company they went with. I’d also be interested to see what the negotiations did for their final TC.
MARVEL CAPTAIN AMERICA Illuminated Masterpiece Sculpture
I didn't hear the author encouraging anyone to live like a victim, just vividly recounting a fucked-up situation and I totally empathized with him.

I've seen enough dashcam videos to know that there are racist cops out there looking to escalate situations to the point where they feel justified shooting a black man. How could the author "understand how police work" well enough that he wouldn't be fearful in this situation?
A 400 foot well? That'd be what, 15, 20 grand, including the casing to prevent contamination? I can see that being a smart move for the dairy farm to offer to neighbors, but that's a ton of money to do on your own initiative unless you're mortgaging new construction. (Better than drinking contaminated water, but still...)
Yeah this argument feels very much to me like "women belong in the kitchen"
> I think they weed out a few, but completely ignore practical development skills, work ethic, soft skills, design and architecture skills, etc.

Tech interviews are not solely whiteboarding. Even at FAANGs there are system design and hiring manager interviews designed to ask about those sorts of things.
> * Your job didn’t miss you before you got there. It won’t miss you when you leave. Do your bit and then go home.

This is very true and, in my experience, when everybody is doing this, it is a symptom of a healthy company.
Genetics, but not particularly uncommon genetics. I know so many people who smoked perpetually, drank hard, ate like birds, and lived in full physical health until their late 90s. Look at the Italians! The Japanese!

If I enjoyed smoking and drinking, I'd invest in that nutrition plan long before taking a stab at whatever the "scientists" and "nutritionists" are whoring out at the moment.
> This implies you don't understand what privilege is. It's very literal. There is no blame in having it. It's not an "us vs. them" thing.

And that implies you don't allow for those who reject the very political and racist concept of white privilege to reject this presupposition. It's not a matter of "understanding"; he's not failing to understand privilege, he's rejecting it and thus doesn't like her pushing those politics on him.

> So?

So he doesn't want to hear her whining about how white men are to blame for bad things that happened to her because he probably doesn't like listening to racist drivel.

> Partially sounds fair if they did a lot of it. What's the problem?

The problem is such thinking is fallacious. Just because bad things happened to her, and white men did it, in no way implies they did it because they're white. They probably all had hair to, does she blame all men with hair? Or to put it more scientifically, correlation isn't caution. What people call white privilege, generally isn't; usually it's just majority privilege which has nothing to do with whiteness and more importantly is not a bad thing at all.

> That's political?

Yes, it was; you don't think it was because you don't accept your own beliefs as political beliefs but rather as reality.
Overlooked Organisms That Keep Challenging Our Assumptions About Life
No, you're not screwed either way, because there are trillions of trillions of trillions of possible 20-character passwords. So even if they can get one trillion attempts per second, it will still take an attacker trillions of trillions of seconds to brute-force all possible 20-character passwords, which is longer than the lifetime of the universe.
A lot of genomic tests only sequence the single base pairs that happen to contribute to that 0.01 percent variability. The article cites that only a subset of the genome was sequenced and that subset isn't chosen at random but rather highly targeted to get at variance in populations
> publish a list of 20 trillion alphanumeric passwords, each of which is 20 characters long, your thesis is that no one should ever use any of those passwords again?

No because they each still have a very low probability.

You have to be Bayesian about this: a list of one trillion passwords that have no further distinguishing information about each one of them cannot be assigned a probability of > 1/(1 trillion)

In a data breach, a given password appears next to a particular username or email, which means it has a very high probability of being the password for that account.
How does your sugary endocrinology align with OTC NSAID use? Comorbid or nah?

https://www.ncbi.nlm.nih.gov/m/pubmed/29311296/
I don't understand your comment. Was the parent suggesting BFS (or the like) is an exceedingly difficult concept to grasp? And if we're going to claim understanding BFS is like understanding zero, then wouldn't that just mean it's just as silly to complain about a question on BFS as it is to complain about a question on zero?
You need less people with cloud is objectively true, as long as you do it properly.

If you're simply running EC2 instances with your same off the shelf software, you're not doing it right, but you'll still eliminate your entire datacenter physical facilities team and server install/rack & stack/replace failed disks team.

If you do it properly, it's incredible what you can do. I have a client with applications running in Ireland, Frankfurt, Singapore, Tokyo, and the US, totaling around 50 EC2 instances running containerized workloads that automatically heal, APIs that are accessible globally and won't go down unless 6 AWS regions simultaneously fail, about 30 static websites, DNS hosting for a dozen domains, monitoring, auditing, and log analytics for all of the above. I set it up in about 3 months as a single engineer and manage it all with about 8 hours a week of total effort. The cost to my client is basically the same as hiring a single senior engineer, but they're running infrastructure that would have taken a team of 3 shifts of IT professionals without the cloud.
I think it is good that you can set your own preference for font size rather than that being defined by the webpage designer; my own preference is much smaller than 16pt. I also dislike the narrow page width, and prefer it to fill the window; it should be the user's job to set their own preferences (there are browser extensions to apply your own CSS to webpages; I use this to alter the styles of many webpages, including even Hacker News).

I generally design webpages with no CSS at all (and no scripts either); it can use whatever preferences the user has set in the browser configuration, instead.

I agree there are too many useless images. I say: do not include any images at all unless it is a major part of the article. Stock images are not helpful. (Again, I sometimes use CSS to suppress them.)

I agree with you no popups, no fixed headers/footers/sidebars, no popup share icons. (Many kinds of share icons should be outside of the scope of the document anyways; you do not need to include them at all. The user can use a browser extension or bookmarklet or something to do sharing if wanted. Anyways, the document author does not necessarily know what the user wants to share, with whom, and how.)
Is this significantly worse than food being subject to market forces? Both are needed to live.

I dearly wish there was enough food and water to go around (and the data says there likely could be, if people in developed nations changed our lifestyles†). But, here we are. Drinking water is likely to become more scarce in the future if we don't get climate change other control.

†I'm 100% complicit in this too, btw.
"Lazy" obscures the addiction component, yes. But no other addiction has such an accessible and accepted narrative that the addiction is not your fault, there's nothing you can do about it, and so you shouldn't even try to change.
100% agree. Haven’t been trying to suggest otherwise. Firmly in the camp that mentioning Flutter is more than enough, and discovering what it is should be left as an exercise for the reader. This all started because I was mildly disputing that this was only of interest to someone already interested in Flutter itself, as opposed to the problem space.
100 Years Ago, Psuedo-Science Industry Quietly Paid Meat To Blame People (2105).
MySudo used to be a free option for up to 9 VoIP numbers but they’ve moved to paid plans (1#/$1/month, 3#s/$5/month, and 9#s/$15/month) [0].

[0] https://mysudo.com/plans
I fail to see it's remotely related.
Wasn't Steve Jobs a Zen Buddhist?
Editing since I misunderstood you:

If you publish one trillion passwords from a large space then each one of them gets a probability boost (of approximately 1/1 trillion), though not enough to ban them, especially if they are not actually associated with accounts.

The danger with using a rare but breached password is that there is actually quite a high chance that it was breached from your account elsewhere.
It doesn't really provide extra security for processes managed by the Linux kernel, but it allows you to co locate Linux and some other code. I could see a model where you have an untrusted Linux land running next to some unikernel like rtos-esque components that are protected from the Linux side. The sel4 guys had a CTF where they ran hard realtime heleicopter software next to a Linux kernel on the same system, and gave you a root shell to the Linux side to start off with.

That being said, last time I checked even sel4 wasn't really hardened against Spectre attacks.
But still “data structures” in the context of most businesses are more Domain Driven Design “Domain Contexts”, “Aggregate Roots”, type structures than any type of complicated CS type data structures.
>at least one of them should be reliably repeatable

The entire idea is that a conscious mind is controlling things. The only truly repeatable aspect of a conscious being is their reflexes, and you can't hammer God in the shins. There are no predictions that you can draw from theism, so it can't be falsified or supported. The idea that you should look for ideas that yield predictions, although it is obvious to us now, took thousands of years to develop.
Was he deathly allergic to bee stings?
Neither BFS the concept, nor 0, the concept are particularly hard to understand. That's why I used the word "concept". If you disagree with that, I'd be interested in what you feel is exceedingly difficult about the breadth-first search algorithm to understand, or if you prefer, to explain why the time it takes to discover or first write down a concept is strongly correlated with its age.

Consider that BFS was first published in 1945, while the turing machine was published almost 10 years prior. Is BFS an implicitly more complex concept than a turing machine? That seems like a strange argument to make, but I'm certainly interested.
Why is it inefficient? Is the HIBP API too slow? How slow is too slow?

My principle is that you should not let people sign up with breached passwords at all - don't make judgment calls about which breaches matter, and whether you think it's the same user or not, or the password is strong enough or not. Just ban the passwords. (Remember that no actual data breach contains 20 trillion passwords.)
Now keep in mind that 1) it is possible to choose a strong password with fewer than 20 characters, and 2) most people will not choose a password that long.

Extrapolating further, this "policy" would disallow people from choosing passwords below a certain length, because it's theoretically plausible someone has published the set of all possible strings fewer than n characters long.
Reiterating my view, I feel like the interviewing grind has become akin to gymming - you go to your mental gym, build up your 'muscles' by doing pointless repetitive tasks AKA algorithms you'd never use in real life (probably like how bodybuilders would never need to deadlift 125kgs in their daily life). It doesn't directly help you do your job but you know bodybuilders have higher than average fitness levels. So in the same manner, devs grinding leetcode probably have higher 'fitness' levels (mostly a type of muscle memory for programming) than devs who don't.
Really? I'm trying it now and finding it tremendously challenging to eat adequate calories without either grains or lots and lots of meat.

Vegetables are so calorie-poor and expensive that they're untenable, so you better love beans and lentils, because that's the vast majority of what you'll be consuming.
Short answer: "don't be silly, too many hard things in the Linux Kernel get correct in Rust"

What they should look into is trying to build eBPF and XDP in Rust. Then you get that compiled language speed and safety in the kernel.

A few quotes:

"I view OpenBMC as on its knees with tears streaming down its face begging for someone to please rewrite me in Rust, because if we're going to have a BMC that's going to hang out a socket over the internet, God forbid, or even over the network, I want that thing to be in Rust."

"That the beauty of Rust is its ability to interoperate, cooperate, with native systems or C-based systems; allow for vistas to open up."
communication with friends or family in china, mostly. when most common western social media has no foothold in china - or is simply blocked - getting a wechat account is the simplest way to stay in contact.

and i'd imagine most of those people don't care much if the chinese government is spying on their baby photos or vacation albums.
If you have a password manager you can and should create passwords that are completely safe against offline brute force. 20 characters works for that. Nothing has 2^119 computation power to break it.

Blocking a list of 20 trillion passwords is probably overkill if you have a slow hash. But with a fast hash it's the difference between "impossible" and "less than one GPU-week".

And if it's easy to block, you might as well do it. There's no upside to letting people use already-posted 20 character strings.
I think we're reading the question differently - I'm responding to the question of, what if you publish a tiny subset of the passwords, 20 trillion out of 0.7 trillion trillion trillion. That does change the probabilities.

I do agree that if the entire space of possible passwords is only 20 trillion, that doesn't change the probabilities. But there are over 20 trillion eight-character alphanumeric passwords. So, I would actually say you should ban them all, because you should insist your passwords are at least eight characters long. :-)

Edit: yes, agree, in practice the probability boost is not very much. I'm just saying you may as well ban them on the assumption that the HIBP API will do so at its current level of performance. (20 trillion is a ridiculous number, because it's much larger than any possible breach and yet much smaller than any meaningful password space, so any arguments about it are going to be inherently silly in some fashion. My current silly assumption is that the HIBP API is capable of ingesting 20 trillion breached passwords with no performance hit.)
I need password fields to:

1)not silently fail when I try a 64 character (or 32 character) password

2)not fail and say my password is "too short" when it is 32 characters and you have an unrevealed maximum password length of fewer characters than that.

3)just all-around quit failing when my password is totally fine, it's a quasi-random string of letters, numbers, and symbols and I'll never type it...

oh yeah

4)don't disable pasting in the password field

4b)IF you do, freaking let me see what I've typed. I promise to not enter the password in a place someone can shoulder surf. Trust me that's WAY down on the threat list for my life.

Then, and only then, if you really want, keep me from registering with a breached password. But you had better tell me that is what is going on.
You're right, it does.

What happened was I skimmed the article looking for support of what you said, and didn't find it initially. But then again, my eyes tend to blur when reading BI articles.
That’d be terrible as the language version changes semantics.
> exact password is being reused is, by itself, strong mathematical evidence that it's the same user

yes, exactly.
Again, I would encourage you to look up demesquitas "logic of political survival." It provides the foundation for the view, and isn't really something one can intuit without familiarity with the model.
Benthic software makes a really nice sql editor for oracle. “Golden”

https://www.benthicsoftware.com

Inexpensive and light weight.
Google faces renewed protests and criticism over China search project
B is for Banned
Here is the actual study it is referring to: [Doing despite disliking - http://images.transcontinentalmedia.com/LAF/lacom/disliking....
You are responsible for what you eat, you are responsible for breaking your own addictions. Pointing the finger at sugar sellers is just a way to wallow in the avoidance of accepting responsibility for yourself.

Want to break a sugar addiction, stop eating, fast until you've broken all food addictions and shed much of the stored calories, and then build up a better diet when you start eating again.
That always struck me as odd, testing aptitude by memorizing others hard won knowledge.

Who could really solve these problems, error free, on the spot with no prior exposure to underlying concepts?!?
Yes it is possible.
MakeCode Arcade: Retro Gaming, Modern Programming
Being able to make a clean interface, as in a clean API, or useful one, is a data structures/algorithms problem and often a distributed systems problem. Many API's are technically impossible to use correctly. For example they might not let you do two things atomically that need to be. Or they might suffer enormously because they don't version their information properly, resulting in client/server disagreements over the nature of reality that are impossible to avoid. Or you get components that are impossible to interrupt cleanly or shut down safely.

It's not the same thing as some piddly twenty minute problem -- it's harder, requires some experience, and it has the same kind of aptitude. Consider it a rule that people that can't handle data structures problems are going to create systems architecture problems.
And transaction fees
Does this method still bypass the algorithms interview? It seems like it only gets your foot in the door, which is probably the harder part for most.
> Extrapolating further, this "policy" would disallow people from choosing passwords below a certain length, because it's theoretically plausible someone has published the set of all possible strings fewer than n characters long.

Yes, that seems like a good password policy. A list of possible alphanumeric strings that is actually reasonable to physically publish (i.e., not 20 trillion) is a list of extremely short alphanumeric strings. 5 alphanumeric characters is 380 million possible strings. 6 is about 2 billion. You should absolutely ban passwords that are 6 characters or shorter!

In fact, I would go so far as to say that the questions of "Is this password too short because someone could brute-force all the possibilities, even if we're using a good password hash and a previously-unknown salt" and "Can someone physically enumerate all passwords of this size and put them on Pastebin or otherwise get them in the HIBP database" are equivalent.
Thanks for the reply. You and the others have really lost me about the differences and compatibility of Java, JRE, OpenJDK, sdkman, conda??? Maybe I'm in the middle. I pay enough attention to not want to deal with Java, but I don't know well enough to find other non-Oracle ways. I might research all this someday and lose my distaste of Java.

Gave my honest thoughts on this and lost 3 karma points. Not too bad this time. I still have a few more to spend.
What benefit does Octave have over the Python ecosystem? Esp as a clone of proprietary software?

The only thing I can see is as a way of running Matlab codes in clusters on cloud w/o having to also run the license servers.
I absolutely want it locally, preferably inside my IDE where it's providing type hints, allowing navigation to type declarations, and alerting me immediately to typing issues live as I'm coding.
> If, by analogy, you deal in second hand cars, it's a reasonable business model to buy virtually any car so long as the price is right and you know who to sell it to.a

Very good analogy. And true. My dad used to own a used car dealership back in the day. He bought pretty much anything he could get for a good price that was in decent shape. If he only bought cars that were in perfect shape, he'd have pretty much no cars on his lot.

And I've worked for companies whose bosses are so damn picky about who they hire that they would go without hiring a single person even after conducting hundreds of interviews themselves over six months, as the rest of us were struggling to keep up with the workload.

It got so bad one time the higher ups eventually had a recruiter just pick a few people and said "Here, these are your new employees. Get them up to speed." and he just had to accept it.
Just a quick point that is worth considering: If a user types in a password and that password appears once in the HIBP breach list, then it is extremely likely that the source of the password in the breach list IS that user.

If it appears 2-3 times, then there is still a significant chance that that user is the source of the password getting into the HIBP database.

And if that user is the source, then the bad guys most likely know that user's email and password, and their account is wide open.
> Because the damage when hiring a bad candidate is much higher than the damage from missing out on a good one!

I get that this is the conventional wisdom in a subset of this industry, but in my experience this "truth" does not have as much objective support as the people who keep repeating it think it does.
The title reminded me of The Art of Prolog. Also pretty awesome book.
Yes, my understanding is that the parent comment is complaining that since it took people with phds years to derive an algorithm for the first time, that we should never expect anyone to implement one in an interview.

But, as with a concept like 0, making the cognitive leap to understanding that there should be a way to represent the lack of something is counterintuitive (indeed, consider Tony Hoare's billion dollar mistake. The "right" way to represent the absence of an object is a hard problem). However, once you've been exposed to it, it's not particularly challenging to rederive the necessary pieces.

So yes, complaining about BFS is, imo, akin to complaining about being asked what the result of the arithmetic operation `35 - 12 - 23` is.
> Why should size of the company matter?

It's not about the size of the company. It's because there is a glut of bad press about facebook currently. This is an example of a mild story being blown out of proportion to garner clicks, because it's fashionable to hate facebook at the moment.
It turns out that interviewing is hard, and we don't know what works well. Most of us think "we" are the ones that can obviously see what's wrong and everyone else is interviewing poorly. Most of us are wrong.

Cowen’s Second Law: There is a literature on everything. Hiring is no different. Why do so many of us that say “of course you shouldn’t reimplement timsort, stand on the shoulder of giants” either make up an interview process based on gut feeling or cargo cult one based on what we heard google does?
This is a terrible idea which will backfire.

Many users have a "universal weak password" for sites that don't really matter, now you will be forcing them to jump through hoops just because so.
Pixel Creator
I'm curious, in your view, why should protocols not use "oneOf"?