61 karma · joined June 11, 2021
Turns out, most people value you less if you give away your time and energy for almost free, instead of value you more.
For short times it might be fine, as the initial welcome may still balance some of that. But any longer term and you’ll likely feel an imbalance.
I'd like to add that, perhaps surprisingly given how niche a field it is, the interactive fiction community keeps producing new languages and tools. In recent years, two new parser game programming languages have appeared: Dialog by Linus Åkesson (https://www.linusakesson.net/dialog/docs/index.html), a full-featured language inspired by Prolog; and Gruescript by Robin Johnson (https://github.com/robindouglasjohnson/gruescript), simpler but focused on creating web games, playable without writing, with a verb+object model like parser games.
There seems to be a logical mistake. Food production is not primarily to fight starvation. Because of the increase in available food millions of new people exist. Without it they wouldn’t have existed hence not starved either. Humans, just like animals, adapt to their surroundings. With more available food the populations grows, with less it shrinks.
I do think everything can be measured given the data, and hence automated. The problem in the latter case seems to me that the data is not easily accessible.
I doubt HR people are on a coordinated mission to revenge their own suffering by letting new candidates suffer the same horrible LeetCode fate. Instead, I rather think LeetCode is chosen because it’s the easiest way, the path of least effort, or laziness.
Note, this is different from freezing. If you’re too cold, you’ll run into different problems like getting slow, getting weak, not being able to sleep, or getting ill.
After the What, it is straight up about the How. It shows me how some hiring report looks like. But it misses completely on the Why. I don’t know what problem the tool would fix for me.
The HN post for example explains the problem much better:
- companies have even in the best case of not doing stupid LeetCode only low quality, unmaintained, unchanging coding problems because it’s valuable time spent not on the actual business. Outsourcing to a centralized service allows for high quality, maintained, and frequently new coding problems. A service precisely allows that not every company must redo the work again and roll their own.
- interview can spend more time on the human, less time on the work. Getting to know the team and the company, culture fit, etc.
IMO this should be the headline. And only after that the nitty gritty details about the How like how the report looks, etc.
If you have expertise in a field you can normally guess pretty quickly when someone bullshits their way through or actually knows what they’re talking about.
But your hiring staff usually don’t have any or deep enough expertise for the field they’re hiring for, which only gets worse the bigger and more advanced your company gets.
But your employees with which the new hire will be working with should have this expertise (or again your company has a problem). So they will find out pretty quickly if the hire is a fraud or not.
Cheating surely creates costs but not as much as you suggest. And as others have mentioned above it is surely not as widespread as you suggest, limiting the cost further.
Any decent employer puts the new hire on a trial period first. During the trial period, the employer should task them with real work. When the candidate doesn’t deliver, the employer can let them go. When they do deliver, the employer can keep them.
In both cases, does it really matter if they cheated their way in or not? No. Preventing cheating is the wrong place to optimize.
While we’re here, dumb memorization of LeetCode style Q&As instead of deep understanding of underlying principles can be seen as cheating just as well. Doing actual work is better in every way.
And many employers already do exactly this coding work already, just manually. They make up a problem themselves, and give you a time limit to commit a solution without checking if you’re cheating or not.
Litebulb just automates this, by taking over the creation of the problem and the analysis of the solution. There’s lots of advantages of the centralization of this, like creating more problems, fixing and updating existing ones, etc.
Provided the problems and the analysis are as good as advertised, I think Litebulb has a great value proposition. I wish them success and hope they can have a lasting impact on the hiring process for software developers.
It makes no sense for Russia to start shooting at a useless office building. If they wanted, they’d drop a few bombs on the critical infrastructure and that’s it.
Maybe the rumors Ukrainian forces evolved them into an attack and planted the fire has some substance? This news is the perfect headline to further lure in the west to help, without any actually critical damage to your own land.
When people are convinced that there is only one way, then the propaganda worked.
Though maybe in the move to the password less future with WebAuthn integrated into operating systems this may become possible.
It’s not a great standard, lots of variation and duplication, and above all undefined. But it’s what we have.
Agreements are but one use case of spoken language. Therefore you’re looking at reinventing language itself.
Not a bad idea at all. I do think we eventually get there. But it may take years and may need more advanced technology like AI. Until then spoken language it is.
Inventing Node before Deno. Creating a compatibility mode in Deno to run Node scripts instead of a tool to port Node scripts to Deno. They even maintain a tool to convert Deno scripts to Node. You really can’t get it more backwards!
I sometimes look at his GitHub issues and PRs and wrong ideas are not rare. Thankfully he assembled a good team that double checks him and catches most of those wrong ideas. But they can only catch so many, and it’s likely more difficult for the executive decisions of the Deno company since money is directly involved like creating a Node compat mode.
Cloudflare Durable Objects is exactly this.
PS: I don't get why that tweet about making tea is relevant at all.
The happening is projected on the year of 2042, not 2049.
Anecdote: for me, the most amazing discovery was a woke slogan found in... Gentleman's Quarterly.