skysight-inc/HackerNews huggingface dataset:
Eh, there’s nothing here, yet. Apple previously attempted this with iAds and they were trash due to the privacy measures then. Their news app allows the publishers to have ads as well and it’s still trash, and fairly private. I’m just confused in what’s the argument, is it that apple is also doing ads or is it the privacy aspect? Cause I will for damn sure take Apples mess v. Meta/Google.
> I once interviewed a candidate[1] who had printed off a whole list like this and insisted on grinding through the whole thing. It was weirdly offputting, but he was such a monster programmer that he was already a clear hire. It gave an insight into the thoroughness of his nature though and showed that he was absolutely perfect for the (critical) role we were hiring him for where mistakes were extremely costly.

Would you share some more information on what kind of role it was? And what kind of qualities would you look for when hiring someone for that kind of position?

I aspire to work in such role (where pedantry is appreciated, instead of tolerated) one day, and I'd be grateful for any such information or hints.
> If what source control or oss libs we use are a dealbreaker

Have you ever worked at a TFS shop?
I can't imagine asking "how verbose is your logging?" in an interview as if that's a question that's germane to whether the position is a good mutual fit.
That's what I mean, physically blocking the route, threatening sure but I'm calling anything short of actually doing (or attempting to do) the sinking 'non-violent' but I acknowledged others might not so tried to explain what I meant. The semantics of what constitutes 'violence' was really not my point.
Fun story with legendary status that's clearly not meant to be taken seriously != a pile of lies.

Offensive, scummy, barrel scraping clickbait nonsense.
Once this changes the prospective employees will turn to other application strategies such as depicted in the famous graphic "will code html for food".
This is the best interpretation of this list. It’s a great guide to understand what topics you care about. Maybe there are a couple questions in here that would raise red flags for you. You should pursue those as conversation points.
Because conferences have submission deadlines. :)
I’m saying 1/3 of men being without women will lead to violence. Or an even more extreme police state than now. Or both.
WhatsApp for versioning, first time I hear, that’s a new one!

(After all why not, there is even e2ee built-in!)
Yeah that was my thought. They were drinking whiskey and everything else washed into it.
Are those the models that assume that all indoor economic activity is unaffected by climate change?
Cows eat grass and have evolved to eat grass. They do not need to eat grain.
Maybe this inspired The Pogues' classic "streams of whiskey" https://www.youtube.com/watch?v=mPpGp_J3z2A
So I recruit ... A lot. If a candidate just ask canned questions or kind of not super relevant questions like this I might spot that as a red flag.

Also those questions are very developer centric, not company centric Ie. Is this environment good for me developer, which is ok but you need to balance it.

For example:

what is your current pain points in the company?

How do you think I could help your company if I join?

^^ it is a huge red flag if you get BS responses on those as a candidate. Every single company sucks or way or another and if they hire it should be to improve it.
All my hobby websites I own have all these in-app browsers blocked.
The author said that, we don't know if the mentioned person does it.
for RSA signing is more expensive than verifying

for EC algos it's the opposite
I think mcelog/rasdaemon deserve a mention there in the RAM section?
Video Shows Russian Military Vehicles Inside Building at Ukraine Nuclear Plant
If you’re good enough to ask these questions freely at interview without fear you should be applying for a more senior role.
To be fair, any other platform could easily outdo Spotify in this regard, if they publicly documented their internal API. :D
> There are a lot of fields of study that we accept despite these flaws. Economics and social sciences are prime examples.

Who's we?

I'm sick and tired of people saying this. It sounds like this: "This is a map of Middle Earth, not Stalingrad." "But at least we have a map! What's your alternative, you complainer?" "But it's not a map of a real place!" "We'll use this map - flawed as it is - to plan our invasion of Stalingrad."

I want my science rigorous. Or else it isn't science.
We're not.

We're struggling with the decision of letting a one handed man identify as two handed and vice versa.

The utter most ridiculousness of this mental gymnastics is calling women "womb carriers", that the sex treated as a baby incubator would have a problem with this is beyond some people apparently.
i dont know... is there money to be made in DeFi? i was busy with some work back during when whole doge-elon and before that, chia and the likes of nft thing surge.........

defi, at least in my understanding did what? they give you bonkers interest on a falling asset so the first one out makes money, kinda like what a pyramid scheme works so how are these projects working?

i mean i have read some stuff, whitepapers and all but they all sound the same, start using hyper technical words in an attempt to sound "complicated" but explainitlikeimfive anyone?

DAO is same, like they project decentralization but recently news of one DAO saying they have to shut up shop because of US sanctions? whats that about? if they are creating money out of thin air, how is US sanctions going to affect them unless it is tied to conventional banking channels?

i heard back many years ago a saying "while people were busy mining for gold, i was busy making shovels", i feel most of the whole crypto is like that. i could be wrong but its just how i feel.

if the concept of crypto was decentralization for the most part, why are more and more tech coming up with centralization?
i want to make shovels but where do i start?
Fertilizer is made using energy, this is a critical distinction. The only consumables in the Haber process are air, heat, and pressure.

Ammonia production can be designed to run when energy is cheap, free, or negative in price, this is unlike other energy-intensive industrial feedstocks such as aluminium smelting.

It isn't currently economically efficient to run factories this way, but (again, unlike smelting bauxite) it is physically plausible to start-and-stop Haber process plants on a scale of hours.

Nitrogen fertilizers cause their own cascade of second-order effects when they leach into the water supply, but this can be solved with well-understood chemistry which renders the nitrate largely insoluble in water but available to soil microorganisms, who are happy to share it with crop roots.

My point is that fossil fuels aren't a feedstock for the most important fertilizer, so the use of fossil fuels in their manufacture is instrumental rather than inherent.
Old grease, you probably broke the sticking just enough for the motor to overcome it and then after a bit of turning the grease warms up enough that it will liquify.
>You'd still write code and test-cases to deal with the not-A-or-B instances, right?

I've seen this one before. It was called the something something solution and was very popular in Germany a while back.
These hardly seem like good questions:

> What percentage of the company is non-male?

> What percentage of the company is non-white?

> What percentage of the company is LGBTQ?

If those things are important to you, better to ask something less bigot-ey, like:

"I like to work with diverse teams. Can you talk about what kind of diversity programs or initiatives the company has?"

It's bad form to single out a specific race or gender, even if it is the most hated trio of white, straight, male (/s). It's not the virtue signal you think it is.
> Anyone who is saying that is obviously wrong and of course I am not claiming that

This thread has fine examples of people doing just that, I did not invent it.

> Why is it uninteresting? To me as a physicist this is thoroughly interesting!

It is interesting in that it’s an example of QM agreeing with classical EM theory. The opposite would be quite an issue actually, because it would mean that QM does not behave at the classical limit. There are lots of other examples of QM agreeing with classical mechanics, there is nothing magical about polarisers.

> the wave description of light is complete and still totally preserved in quantum optics. The only deficiency is that the light's energy density should be quantised.

In a narrow range of quantum optics maybe. I work on radiation/matter interaction, and you definitely cannot account for a lot of things if you posit that light is a wave. Unless you add some particle-like characteristics to your wave, in which case it’s not much better than assigning arbitrary wave-like properties to a particle.

> You absolutely should not think of light as infinitely small particles that move at the speed of light

I don’t.

> that is an inaccurate and outdated picture

It is not a wave either. The problem is when we try to pigeonhole it in either character. I mean, really, are we arguing the whole wave/particle duality concept again? That was novel a century ago.
See the Abstract and Section "1. Purpose and Scope":

"Over this time, a number of changes have been made to TCP as it was specified in RFC 793, though these have only been documented in a piecemeal fashion. This document collects and brings those changes together with the protocol specification from RFC 793. This document obsoletes RFC 793, as well as RFCs 879, 2873, 6093, 6429, 6528, and 6691 that updated parts of RFC 793."

"The purpose of this document is to bring together all of the IETF Standards Track changes and other clarifications that have been made to the base TCP functional specification (RFC 793) and to unify them into an updated version of the specification."

Nevertheless, it seems that some updates and clarifications were also done:

"It updates RFCs 1011 and 1122, and it should be considered as a replacement for the portions of those documents dealing with TCP requirements. It also updates RFC 5961 by adding a small clarification in reset handling while in the SYN-RECEIVED state. The TCP header control bits from RFC 793 have also been updated based on RFC 3168."
Can you demonstrate that claim ?
Given that we're talking about whether or not the passport should have additional options, and are citing this % as a reason for providing additional options, it's important to ask:

Q: How do we know that the people who want more than 2 options for sex are, in fact, these same 0.018% of the population who have DSDs?

In my limited experience, they are not the same people at all. Clair [https://differently-normal.com/author/clarecais/] has CAIS, and has "F" on her passport. Statistically, non-binary people have no DSD, and are unambiguously either M or F but wish to identify as something else. Therefore making an arguing for additional options in the passport sex field using an intersex stat is precisely what Clair complains about in her blog: ie, she's pulled into a fairly toxic social/political debate by a group that wants to use her condition for its own gains.

Clare is one data point of course, but her slant tallies with the assertion that "arguments made using this group and trying to apply it to society as a whole is likely not made in good faith".
For 110 years, climate change has been in the news
I think most of these need to be up-leveled to being open ended like “tell me about your development process” or “describe my role in the organization”. Even then differing questions will be asked to various interviewers either with you guiding the conversation or asking in Q&A at the end. I mean, is your entire decision going to be made on GIT being used?
> This new version of STD 7 (TCP) was adopted yesterday.

To give an official source for that: https://datatracker.ietf.org/doc/rfc9293/ says "Last updated: 2022-08-18" which indeed was yesterday.
Web pages have a timeline in the form of a scroll bar on the right
It could be rewilded, instead of being used by humans directly. Biodiversity badly needs that.
The shockwave from a sudden release like that can take out the better part of a raid array in a matter of moments. I never understood why they have to release it all at once instead of gradually because the number of times that I've seen accidental releases dwarfs the number of real firefighting incidents.
What YouGov About is describing about their collection methods.
What class with Startup cultural and tech workers in general. I remember when workers got time and a half for overtime. Never "professional" workers. Gee, thanks for the badge boss. and people same gamification doesn't work.
What does this April fools joke have to do with the revision of the TCP standard?

EDIT: Also consider that the "evil bit" is part of the IPv4 header, and not of the TCP header.
3) Grazing animals are good for carbon capture, as they need grass to graze, and grass is one of the best carbon sinks.
It was squarely mid-flight/cruising, international IIRC. We were nowhere near landing/approach.
Not that I disagree, but if the interviewer expects the candidate to spend the better part of a week proving that they know how to code, whats so outrageous about asking for a day?

You see this a lot, companies with insane hiring processes so they "only get the best", and then won't even do the basics on their end like listing the salary.
> Just like Windows support.

Completely non-existent? Either a laptop comes with windows or you get zero support. See every chromebook ever.
I'm not actually a huge fan of the word "micromobility". It makes it sound small, like it's only for going just around the corner or something. But long before the introduction of electric bikes, people have already been using regular bikes for lots of travel within cities, and even outside it. Electric bikes make those distances more accessible to people with less stamina, but certainly the faster electric bikes and scooters, and even human powered streamlined recumbent bikes, at perfect for medium-distance travel outside cities.

It's not small-scale mobility; it's just mobility. More efficient mobility. Smarter mobility.
And do other groups, besides the French, that have member criteria other than allegiance to abstract principles, also "deify unreason", as that quote put it? You didn't have such a laissez-faire attitude to member criteria when it came to deconstructing the French identity.

> you're trying to have an argument about it, and I'm not really interested in having it

You were hoping your absurd near-total negation of French identity would go unchallenged.
Ok cool but yeah that has nothing at all to do with what they do. They’re like Stripe. They help you charge cards.
I guess, but its the same problem as Patreon and every other "pay creator" platform: The TOS states black and white that someone can be kicked off the platform for a variety of reasons that amount to "you're doing something controversial and if we take heat for it we can boot you off".

Now at the moment Gumroad is the wild west of content, so far I haven't heard of any big "controversial" creator being booted, but TOS makes it clear it is entirely possible, so I guess so far so good, but Patreon was also very relaxed until it wasn't.
The recommendation I read back in the 90's in Code Complete that has served me well ever since was that variable name length should be roughly proportional to the variable span. "Variable span" being the distance between where the variable is first defined and its last use. Generally that means that a temp variable inside a short function can be a single letter since you can see the full context of its entire lifecycle right there and it's unlikely to be confusing; indeed, a short variable name in that case will often be much easier to read and work with than a longer one. OTOH, a global or exported variable that might be accessed in different files from where it is defined or used across thousands of lines really needs to be descriptive enough that anyone encountering it should know what it's for without having to backtrack to where it was defined. A variable name that's a few words long might be entirely appropriate for that. A corollary is that a large variable span is often an indicator of a bad design. So if you find that you need really long variable names to make your code easy to understand, you might want to step back and see if you could set up some better or different boundaries.

I've found this to be a much better rule of thumb than "always use long variable names" or "always use short variable names".
The obvious answer here is to transplant rumen into humans, thus cutting out the middle-cow.
Serving Netflix Video Traffic at 800Gb/s and Beyond [pdf]
I imagine border control find it helpful to have sex on the passport because in 99% of cases it’s an easily observable identifying characteristic.
No, that's not how it works. There is a chance that one of the first 3 candidates is the best one, but as the total number of candidates increases the probability of that being the case decreases.

Different failure mode for this algorithm is when you get your candidates presented in the "worst to best" order - it makes you set your threshold low, and then settle for an average candidate.
> We need to go back to our old style of farming before the world wars where we rotated between crops and animals and used the animals dung as fertiliser.

You mean, the old style of farming where our agricultural output was sustained by unimaginable tons of ancient manures looted from South America?

We are already using ~all available animal dung as fertilizer; it provides something like 10% of our global fertilizer needs. We can't produce more animal dung than we are now; we already raise an absurd quantity of livestock, and we especially can't do it while also doing the other thing people suggest on this topic, cutting our meat production by 90%.
Yes, that would've been reasonable, and it wouldn't have been a briefcase. Fifty thousand dollars in hundreds is a stack less than three inches thick.
A lot of the comments in here are reacting to the large list of questions being very off-putting. There's a deeper issue here that we still don't have a good answer for: it is incredibly hard to tell what a company is like until you start working there, and asking questions either leads to very surface-level answers or just flat out catfishing candidates. Companies being transparent and detailed about how they operate is the exception.

The company gets to spend 3+ hours finding out information about a candidate, but the candidate has little option to discover company culture for themselves. They can snoop around on LinkedIn but this doesn't answer much about culture unless there is someone who is prolifically producing content inside the company. There's glassdoor which might answer part of it but generally the reviews there are extremely shallow and biased by the skills, mindset, and treatment of whoever wrote the review.

So what's the answer? I think "ask targeted questions" is fine as long as it is not "ask 100 general questions". I haven't seen a single article on the meta of how to pick what questions to ask or how to get past shallow answers. I also think the entire industry is performing pretty terrible in this space and we don't have a good answer for how to handle it that is common or even well-known. This leads to lost candidates or (intentionally or unintentionally) catfished candidates who will leave after joining.
What part are you referring to? I don't see any FP stuff in that article... It's all imperative code?

Anyway I would recommend learning Haskell. I like languages that allow different styles (like js does to a certain extent). But I think it's better to learn a modtly pure OO language like java and a pure FP language like Haskell to be able to make the right decisions in a language that supports both like JS.
If they aren't discriminating, what do companies need to know the percentages for?

My previously employer advertised the average age of their employees to me during the interview. I later realized they are calculating that metric because they are discriminating against older people. They wanted young, inexperienced flesh like me.
> Furthermore, livestock agriculture is one of the leading causes of the collapse of biodiversity - a crisis that will have much more dire consequences than climate change, in my opinion. Also a crisis that almost nobody is aware of presently.

I see no clear reason why fewer species existing in agricultural production areas will lead to any particular disasters, but I'm happy to be enlightened.
Yeah, it comes up in the news more frequently than you'd expect.

1. Gas truck tips over. Usually with 0 fatalities

2. Locals go over to collect free gas

3. Truck explodes. 30+ fatalities
The performative part is engaging in endless discussions and iterations about internal tooling
It's perhaps important for people to understand that this type of problem is not necessarily a problem of hiring secretaries but rather a mathematical problem presented in less abstract form that people can easier relate to and digest. There could be dozens of variations, one could involve being able to go back one decision point (change your mind on the previous candidate), one could be to use parallelism and multiple evaluators, one could be to not know the total number so you might have seen the last secretary ever, etc.

Most real life problems will never perfectly match to this kind of math problem simply because real life usually offers more flexibility than a strictly defined mathematical scenario.

Reminds me of the joke with the mathematician and the engineer who can take as many steps as they want to get to the pot of gold in front of them with the condition that every step is maximum half of the distance remaining. The mathematician is absolutely livid because he knows he'll never reach it, while the engineer is happy because he'll be there for all practical purposes.
Good point about the increasing demands on Seniors in some regards. (The role might also be changing, such as juggling lots of high-level abstractions and vendor bureaucracy in many domains, with a significant amount of Stackoverflow consultation, rather than lots of experience in lower-level details.)

I'm trying to reconcile meaningful titles with current industry norms.

I'm open to other schemes, but, FWIW, this is my current rough idea:

* First is some kind of new college grad. Some of whom would object to Junior in their title, and I think Technician sends the wrong message about near-term goals, so I'd just call it plain Software Engineer.

* After maybe at 1 or 2 years, they've been through some projects, and they know a lot of the mechanics (big contrast to a new-grad who learns as they unlearn what they got from bloggers). You want to acknowledge that, so maybe it's Software Engineer II.

* At some point, maybe it's 5 great years in, they've seen a lot of stuff, and gotten wisdom and insight, and Senior sounds about right and conventional. This could be a plateau title that someone has for a decade, even as their TC increases quite a bit.

* Staff and Principal engineer roles transcend project teams (more than Seniors do). Large companies will each have their own definitions, and there might also be unwritten meaning. (At my first hardcore software engineering employer, there was no Staff, and only a tiny percentage ever made Principal. By the time I made Senior, the VP asked me where I saw myself in 5 years, and I said Principal... He gently set expectations that that's pretty ambitious, only a few people ever do it, and 5 years would be very fast. Correct on all points, and now I think I have a better idea of how much more the Principals knew that I didn't even know were things to be learned.)