skysight-inc/HackerNews huggingface dataset:
> First, "living on the dole" has a bad connotation. You are already setting social norms as you say it. Implying that it would be shameful to do so. This plays into the idea that people's needs for esteem is driven by societal norms.

It's not an arbitrary "social norm", it's a human near-universal, at least to some degree, to stigmatize freeloading and value at least some sort of productive activity. After 30 seconds of reflection you can probably figure out why, and after a further 30 seconds of reflection you can also figure out how these attitudes are already engrained at a deeply emotional level for many.

> Second, as it stands, those two options don't afford you the same produce and sercices. Working still raises your standard of living higher but what if it didn't, and in fact, paid less? That is the hypothetical I am talking about.

It's not really a hypothetical--lots of people are in either a welfare trap or a disability trap where they are capable of working and would actually like to work, but doing so would jeopardize their eligibility for benefits, and they can subsist off the benefits more reliably than they could subsist off of their work. These people are almost universally incredibly unhappy with the situation.

Furthermore, if you look at other situations--retirement, winning the lottery--where there is no economic need to keep working in order to earn an income, there are still high levels of depression, suicide, and drug abuse that soon follow. This is one of the reasons that people at the top of social hierarchies--executives, politicians, judges--very, very rarely retire once they reach a "normal" retirement age. If you're powerful enough, you can reduce the scope of your actual job to the point that you can still do it. At that point, the main barrier is retaining the capacity to work.

> Third, you've moved the goal post. Because this isn't about the choice between not working and working a bad job. I'm talking about the choice between not working, or working towards a good job. And which one would feel more rewarding?

Let's look at the jobs you pointed out as "bad jobs":

> an oil driller, an iPhone manufacturer assembler, a McDonald cashier, a dishwasher, a house cleaner, etc.

First off, your choice of "bad jobs" alone comes from a place of arrogant upper-middle-class ignorance, because those jobs don't really have much to do with each other.

Oil rig workers have good pay--averaging around six figures, actually--and long career paths with lots of opportunities for advancement (https://money.cnn.com/2012/05/10/news/economy/oil_workers/in...) (https://www.jobsite.co.uk/worklife/work-oil-rig-18734/). Oil rig work is an entire sector of the economy you obviously know nothing about if you're comparing it with washing dishes in a restaurant or cashiering at McDonalds. Just like factory work, farm work, and construction work--nobody thinks its fun, but the people who do that work take pride in it, and are right to do so.

> But the reality is that, it doesn't make sense to have people do things that aren't needed.

There is also no shortage of things that are needed.
I tend to look at a candidate's work history.

If they've worked at least 10 years, as a coder - it's VERY unlikely that they're a complete liar. Especially if you can call former co-workers, or look at code samples they have online on a personal github, or look at their post history on stackoverflow, or things like that.

Even a technical description of prior projects - is a really good indicator of whether they're competent.

Puzzle solving - on the other hand, bears little resemblance to actual job requirements in the real world. It's honestly a dumb way to vet candidates. Would I like to see if a candidate, out of a pack of 5 or so potentially equal candidates, has a better approach to creative problem solving? You bet. But I'm more interested in their inter-personal skills, communication skills, and their instincts towards the ethical challenges we face as engineers. (like: when things go south - and blame starts flying). Who do I want on my team? That's the most important question.
Anyone still believe this shit after the bitcoin pyramid?
Ethereum Node Developer Survey
>
They have kids. Developing a sentient being is a higher priority and more difficult than developing React Redux.

This is like saying: "I have a time-intense hobby that I prefer over working too much for you.".
I agree with you, a code review isn't meant to get the best code ever, mostly because as you said, there's no universal correct way, but it's meant to make sure the code change is doing what it's means to be doing.

What is not clear in your comment though is that that means looking at the code and making sure there's no mistake too in it too.

It may seems like it's working as expected, but maybe you'll find an edge case that was missed by the original developer.

It's possible too that the solution of the original developer was clear to him, or that it's clear knowing the context of the ticket, but once in the wild, that code may become incomprehensible (which later on can bring more error because someone misunderstood why that line was there and changed it incorrectly for example). That can be easily fixed by adding a tiny comment there.

Sure doing what it's supposed to do in an acceptable performance is great, but I think there's a bit more into a code review and ignoring theses can be quite problematic.

> "I can't read it!" - I also can't read Chinese

Doesn't this show there's an issue though in the long term? If you are the only one that can read Chinese in the company, maybe it would be a better idea to consider using English?
If you're interested in this stuff a team i'm in proximity to are working on such problems.

http://www.flucoma.org

https://pure.hud.ac.uk/en/publications/stationarytransient-a...
thanks for adding this depth to your experience.
Have we forgotten all the bland brown cover shooters that weren't successful, or the pile of WWII shooters before that? Somehow the industry and many of the customers continually forget that chasing the latest trend typically doesn't pan out. If I want to play BR, then PUBG & Fortnite already exist.

The thing is, I know I'm not the only person who doesn't like BR, and there's certainly money to be made without a BR mode. Just look at Rockstar, they're doing absolutely fine financially.
Now an experiment with 4 gpu nodes.

Horizontal scaling matters as well, which is not shown here. Furthermore, using less than 16gb of data.. why would you use these frameworks in the first place?

It is common knowledge that a grep and sort on 100gb is faster than Hadoop, however 100tb is a different story
Or perhaps those doing the voting simply don't share that experience?
The "value" is the payment network itself (plus stupid things like rewards which are taken from the businesses and distributed to the consumers). However, the payment network can easily be superseded by the internet, and all that's really needed is to build a ledger on top of it (and using something like PoS it could use an amount of energy probably on par with Visa, or at least comparable to it for the same number of transactions).
We convinced our parents to buy a computer because it would help our education when all we really wanted one for was playing computer games. Joke was on us though, because playing computer games at the time usually involved a lot of putzing around and figuring out how stuff worked, ultimately teaching us marketable skills.
To be honest, almost all the recruiters in NY tell me the range. Some try the 'what are you looking for' attempt at opening bid. But many just want to get on the phone to massage a mediocre pitch, in my experience. Mediocre can mean an annoying location, or below market salary.
For this reason at my company we often do the code review of a junior developer's first pull request in person and in private. I think it's worked decently well to ensure that comments can be the start of a conversation and not a reprimand, and to help the junior to understand that the comments are not meant to be a personal criticism.
If they put in a good CPU and use a standard OS, they would have more trouble selling you a new camera with newer features, since you could just upgrade your old one.
FWIW, I regularly pass interview candidates who "fail" at certain questions. The point of those questions isn't to complete it perfectly (and sometimes we get less information from those, honestly), it's to see how you go about getting there, how you fail, and how you deal with that failure.

For instance, one of the problems I frequently ask has a structure that really encourages people to try inventing heuristics to solve the problem, even though ultimately all of those heuristics fail. Seeing how people react to "but what if your input looks like this?" questions is often very enlightening- can they rethink their approach? Do they just keep glomming on more special cases? Can they deal with someone pointing out that sort of flaw?
Grand Canyon tourists exposed for years to radiation in museum building
So, when you don't understand what they are talking about, your first instinct is to unleash an ad hominem attack?

Way to go. Way to go.
At the end of the day, the question itself is a tool, not the goal. When interviewing, I look at how the person approaches a problem and works through it. I don't really care if they get to the end or not.

People who complain about memorization and difficulty are kinda missing the point. Just like learning math at school isn't really about knowing how to do trig, but being able to think logically and do problem solving.
Almost all the color graded versions seem to have a sepia tone. Is that on purpose?
Hey, thanks for this. I watched this video a few months ago when I was getting started with Magic Lantern. Nice work!
This is an attempt to squash meaningful discussion. The right-wing bias of HN moderators is readily apparent, as usual.
I think you may be confusing that with something else. You can't create a complex game with just CSS. I'd love to be wrong but provide a link.
It breaks the UX of the site - at least sticky a solution so people can read the article
Bitcoin Price Eyeing $4,000 as LocalBitcoin USD Volumes Surge
I can't find a link right now, but a dead whale will move forward at a knot or two just due to the action of its flukes in the waves. Some folks were working on a means to propel boats by artificial flukes.
Well, all I can say is I'm glad my team of developers is not like this. Though there was one code review from my senior engineer going increasingly heavy on asking for documentation examples on a specific function. I felt like he was angry with me but maybe he just had a strong feeling those examples were important... Actually I will never know so time to forget it :)
To start off, I believe that those photos are not fake.

But let's say someone says they don't know if the photo is a fake.

How would you show that the photo is not a fake?

For this question, I wonder if eventually the answer will be: well, we have to trust someone.

I want to say that there's nothing wrong with saying that I trust the photo is not a fake because the person who presents it looks trustworthy.
Researchers Find Further Evidence That Schizophrenia Is Connected to Our Guts
This is a no go in large companies, because the large company wants to avoid 'cliques of incompetence' and personal fiefdoms developing, not to mention all of the other problems people have mentioned.

In large organizations, there are too many people for execs to know everyone, so a standardized but rigorous process is better from their perspective.

I say tech's process is better than many other industries processes, which is outsourcing evaluation based on credential prestige.
React animation libraries
If you're experienced and good you can do way better than 300k at some companies. Also if you think spending a few hours practicing leetcode makes you desperate, wait till you hear the hoops people have to jump through to become a doctor or investment banker.
I ended up in the hospital on IV because I did not know athletes were supposed to drink pedialyte.

Some people lose their sense of thirst when pushing it.
Just to clarify, when I write "unfair" I mean specifically that it is something that public policy should potentially address as a public concern.

There are impediments that should not be addressed by public policy - for example , if young gay singoporeans are less likely to become plumbers because gay culture looks poorly upon plumbers, that's unfortunate but shouldn't be a matter of public policy.
It's readily visible that Country A wouldn't go anywhere without trade, so I don't know why you would think that sanctions and embargoes (which are actively hostile to a country's economy) are a drop-in replacement for protectionism in the model. There are a trillion ways to tie your shoes wrong, and only a handful ways to do it right. It does not help when the one who does the tying is the one who wants you to fall.
if you are male you can go to a testosterone therapy clinic and essentially just say that you are tired and or depressed and get prescribed 200mg of testosterone per week
Which is great, but I could say the same thing of Ferraris for show-off producers in LA, or Hello Kitty backpacks.

Just because one thing is bad doesn't mean the other thing isn't also bad.
The question of whether it should be regulated is part of the big "hard question". Besides, we shouldn't be afraid of having to answer hard questions.
> I wonder if the added friction of changing your place of work caused by this practice is meant to somewhat counterbalance the heavy incentives engineers have to job-hop in the current climate. Kind of makes sense from the point of view of tech employers.

I am not sure what to think about this claim: it is the other company that prevents you from working for them by this interview process. The current employer has the incentive that you don't leave. The other (potential) employer rather has the incentive to poach you.
GDPR doesn't give you any legal option aside from asking your data protection authority.
So in summary: If your company has a seemingly broken hiring process that weeds out good people, bypass that process for people your people judge as good, and keep it for everyone else.

I suggest that it is better to fix the hiring process in the firsr place and just run everyone through it.
Then again I don't think it's that expensive either.

I suspect the problem here to be scale.
Lots of click-baity material here, and plenty to tear apart.

I think the best way to understand this essay is like this: it's all received wisdom based on what we've experienced so far. That doesn't make it right or wrong. It just makes it highly speculative.

Like to see why? Dial back the calendar a few hundred years. Some bozo named Columbus just got back from a trip. He says there's tons of wealth awaiting us in some far-off, plentiful, perhaps-utopian paradise.

Now that we've rewound the clock, you can read through this essay in the same way, substituting the new world for space. It's all the same.

My fear for our species is that 1) we get exactly what we want, ie, we create AGI that caters to our every whim, thereby making our entire species superfluous, and 2) if we don't do that, we argue our way out of exploration and adventure and into introspection and conflict. Who knows, maybe we do both.

I wish this had been a better essay.
Cygwin is the pioneer in Unix on Windows but it's been superseded by the MSYS2. I say this with caution though: MSYS2 is inspired by the Cygwin. But it's just more authentic because you use real Windows applications doing Unix jobs.
It’s happened to me. I’m terrible at the whiteboard in these situations. I have a severe disdain for whiteboard sessions. I’m an experienced engineer, but I’m likely to fumble at the whiteboard.

When I’ve interviewed candidates I make it a point to talk about something they’ve worked on and drill down into it. If they need the whiteboard to convey something, that’s great. We’re having a conversation and I’m not giving them a test. I’ll ask about potential optimizations and/or improvements, but I try my best not to make things adversarial. This has worked out really well. The best conversations have resulted in great hires in my experience.
>totally incompatible with referral bonuses.

I think it's fair to waive referral bonuses if someone is referred through the "trusted referral" process. If someone is dying for a bonus, they can still steer the candidate towards the company and let them go through the technical loop normally.
I provided the link for jurisprudence context, not to support an argument of transgression of the Japanese legal structure.
I think it's not that simple. Latest tools often increase productivity. Gamers can afford to spend days and weeks to add some feature to their favorite game. They don't have deadlines and they don't care about QA. It's another thing when you have to fix a bug or add a feature in a limited time with limited resources because business needs it.
Agree, we just wrote 500 LOC that reads data and a spec, interpolates, validates, and provides a nice error report. This is saving us many many thousands of LOC and hours of frustrations. We are only using it in one place, and will likely start using it in more. Probably want to OSS it first, so be on the lookout for a Show HN!
Started by Trammell Hudson of Thunderstrike fame (and many other interesting projects), see https://trmm.net
Oh dear, bad day in office?
Only two words away from the perfect clickbait title.
You will notice that the second size does NOT fit into GPU ram on this benchmark since we ran it on a GPU that has less memory available than the DATA it is running on. Spark is feeble, perhaps but it is one of the tools being used to feed GPU workloads. Here we have replaced a workload where spark was previously used and now it is faster.
Considering the differences lean towards the DOM interface names for given attributes and properties, I wouldn't exactly call it NOT JS.

It's actually an XML abstraction that closely resembles HTML + JS-DOM, and is then converted into function calls and arguments.

It's also about as close to E4X as an abstraction that I've seen and something I wish was cross browser over a decade ago when it was first introduced by Mozilla and Adobe, but that's a long side-track. In the end, it's very effective and works well imho. Yes there are some more complexity points in some places, but I don't think anything else does it better. Vue imho is comparible, but I don't like it as much and I feel that Angular is far worse in practice.
One time I sat down with a potential hire and went over a trivial PR. Nothing hard just some code to look at on GitHub to provide a familiar environment.

Why? To use it as a way to just look at our tech, get completely off track, and go down the tech rabbit hole. Good devs get really excited and talk about what they're using, what libraries they like, what they'd like to work with, etc.

Best hire I've ever made.
I’d like a Postgres bake off. Playing against Spark on a 24Gb dataset seems silly, too.
I just wanted to add, if I came across as criticizing, that I do agree with you. I do think the county is at fault. I do think people should expect more. I am just not seeing people doing that.

Sweden was never perfect, but some of its reputation as a functional country is not unfounded. Today we have many systems we know aren't working, yet little is being done. I have even heard Swedish political analysts being dumbfounded that some political issues were there are obvious flaws, and should be something that matters to people, don't show in the polls. I guess it might have to do with the political landscape, were there are a large number of people that very likely are dissatisfied. It just doesn't, because of the polarized situation, result in change. Instead it results in whatever is less objectionable, which is mostly whatever made the situation bad in the first place.

Anyway. I hope this incident get some more attention in Swedish media.
Red Pipelines and Build Whisperers
Not surprising at all. Fighters can be shoehorned into doing the B1s job pretty well (before the B1 that's what we did anyway) but that still leaves a need for "just stay up there and we'll call you if we need you" roll which the B52 fills at a lower cost. Basically, if you just dropped one aircraft from the fleet without replacement dropping the B52 would be more painful and save less money so the B1 is the obvious choice.
'Chelsea stars must recognise importance of season
If you have a good model, and can use model-based optimal control which has been understood for decades, then that is good but there's also not really a research problem? You can just do the simple, robust thing and it will work great. (i.e. "to publish more papers" is actually a legitimate reason if your job is explicitly to publish papers)

You may enjoy the article, "A Tour of Reinforcement Learning: The View from Continuous Control". At least that researcher would agree that people doing RL don't pay enough attention to "classical" control.

https://arxiv.org/abs/1806.09460
> acting like it's some kind of trivial solved problem is highly disingenuous

I said it's possible. I didn't say it was easy. That said, PoW on a small scale is an interesting experiment. On a large scale, it's a horrible way of allocating energy usage. So while the databases running on PoW are working, they are a stupid waste of energy.

I welcome any alternative.
>I’m sorry but you cannot do what you are claiming.

But I have. Not in the specific context of a job interview, but I have absolutely convinced technical experts that my level of expertise in a field is above my actual level of expertise. Ironically, if this were a technical interview, I'd fail it, not because I lack the skills to convince technical experts of my non-existent abilities, but because you don't find me trustworthy.

>The point is to recursively keep probing for deeper technical specifics, so they have to explain at finer and finer technical levels what were the tradeoffs, why exactly were certain decisions made or how were certain problems overcome.

But without context, you can't effectively do that. I, the candidate, am in control. I can steer the conversation to avoid areas where I don't have expertise by answering all kinds of things: "investigating that was someone else's responsibility", "well we never tried anything else and our current implementation works well enough that we never needed to", etc. You can't know if those are lies or not. There are all kinds of completely valid non-technical reasons for decisions that may be completely outside of a candidate's control.

You're either forced to completely trust the candidate, or attempt to verify their authenticity during the interview, at which point you quickly venture into the land of bias and subjectivity.
In addition to a shared aversion to voluntarily turning my possessions into billboards, I'd like to add there's real value in keeping computing devices generic looking.

By plastering your laptop with a completely unique combination and placement of stickers one can discover in videos or photographs online from conferences or talks for example, you make it a whole lot easier to pick out your unattended machine from a set, a hotel room, or luggage.

This can easily be leveraged by assisting targeted theft, destruction, or sophisticated physical access attacks.
So much this^^! Like everyone here is saying, interviewing itself is a skill, and part of that skill is how the interviewer communicates and takes part in the problem (or lack there of ). Every point you mentioned is an issue I've seen as well.
They significantly overlap, so wouldn't say they are different. I would suggest that most "JavaScript developers" in the box you'd put them in are backend developers that only know a minimal amount of JS and don't really know JS well and by extension the browser itself.