The difficult part is to do it in the same action as other serves. I used to do it as a kid around 20 years ago, but my action for this serve was different, so easily noticeable.

Dell latitude laptops sleep very reliably. I have had 4 in a row now since 2007.

Also as a side note, as a user, I agree you don't care whose fault is it, but then this is hacker news where we are interested in whose fault it is.

Blame microsoft for it with their crazy si0x experiment breaking everyone.

There's a difference between live coding round and leetcode rounds where you need to perfectly write code for as medium or hard leetcode question in 20 minutes.

1) that’s not what most companies do

2) if you have thousands of applicants for a position, and probably a dozen stand out by passing a really tough bar, wouldn’t you want to find those dozen?

> 2) if you have thousands of applicants for a position, and probably a dozen stand out by passing a really tough bar, wouldn’t you want to find those dozen?

It's a reasonable assumption, but you might not. If the role doesn't actually require those skills you might hire someone who's going to get fed up and leave in 3 months or (worse) who invests time in making their job more interesting instead of solving your actual business problems.

Good points. Most FAANG/MANGO companies in India do leetcode. And I know Amazon still does leetcode in US/Europe.

So, yeah, you are right. Live coding is very good, which is what I do, but too many people confuse live coding with just leet coding.

The question is, however, whether this is a good proxy for one's future colleague and employee.

I have no idea what could be a better option (well, maybe preparing some small feature to work on together), but it often turns out that good problem solvers are not really great at doing the job, for reasons that have nothing to do with the hard skills.

Totally valid critique.

Hiring is really hard. You only get a few hours to decide whether someone will be a good engineer and colleague for several years.

By the nature of the constraints alone, anything you do will be extrapolation, and a guesstimate at best.

Not the OP, but here’s how I see it: freedom doesn’t exist in a vacuum. Whether it’s in society or in software, real freedom comes with some responsibility. You can’t just take, take, take and expect the ecosystem to stay healthy. That’s not how any of this works.

Same thing applies to free software. If we actually care about keeping that world alive, there’s gotta be some duty baked in—some expectation to contribute back, or at least not strip-mine the commons and bounce.

MIT’s blown up mostly because the big players don’t need the broader free software community anymore. They’ve got the scale, the headcount, and the cash to build and maintain their own internal ecosystems. So from their POV, permissive licenses like MIT are perfect—no obligations, no copyleft, no friction.

But let’s not pretend that’s “freedom” in the idealistic sense. It’s freedom to extract, sure. Freedom to integrate and forget where it came from. For a lot of people on HN, that’s fine. But if you care about the sustainability of the broader ecosystem? Then yeah, we’ve got to talk about duty, not just rights.

It's time to learn Chinese. Especially with advances in RISC-V

A bit funny since logographic languages are the original CISC.

/offtop, but could not help... Optimists learn English, pessimists learn Chinese, realists learn AK-74 (or M-16 or whatever one's military is using).

It is common for authors to say that "We are not aware an explanation as of now."

The post by itself is not harmful, since it can be that the person posted it for their own blog because they like to write for themselves. Someone now finding it and using it for their own benefit/loss, that's a problem.

> ~~Someone~~ *An LLM training bot* now finding it and using it for their own benefit/loss, that's a problem.

I believe you meant.

I don't feel any difference in both the images.