fnwx17

The current issue is that most of the effort is done by humans right at the beginning of the process: CV screening & first calls.

If you're a recruiter, by the time you actually get to talk to a candidate, you're tired of screening and most of the time you do a half-assed call.

Plus it boggles my mind how very very few companies train the recruiters in understanding the technologies they have in their stack.

There are a lot of factors that add an incredible amount of friction and make it a very asymmetric process (as other have said above):

• plain human error • job specifications with boilerplate text not being clear on what the role actually does • often times the people doing the first screening don’t have a technical background • resumes come in all shapes and formats, so it’s difficult to efficiently read them

And because of that asymmetry and supply-demand ratio, it’s actually quite hard to hire software developers that are suited to a company, tech environment & business needs.

(disclaimer, I work at WorksHub)

The way we're trying to solve the issue at WorksHub is by trying to get companies to open-source same part of their code-base so that a developer could submit a few PRs during the interviewing process.

This solves the issue of irrelevant technical interviews, gives an idea of how your coding environment will be right off the bat.

Basically the thing is to do as much of the process as possible using only tech and then leave the last part for the actual human interaction.

I've almost completely switched to decaf coffee (which still has 15-30% the amount of caffeine normally found in regular coffee) after reading "Why Do We Sleep" by Matthew Walker.

And half of the office here is either reading it now or wants to start reading it

> Ugh why did he have to ruin it with the block chain. He probably has enough solar and battery capacity to power all his nearby neighbors every day 24-hours a day

Technically, it's mining cryptocurrencies. Probably at peak crypto mining profitability (around Dec-Jan) it was making significantly over what he could sell to the neighbors; also implying his neighbors would just switch to his infrastructure, that would be a bit of hassle.

Maybe if he hooked up all those GPUs to a render farm, it would be an alternative.

brilliant comment. I literally just hit the reply button to tell you that

> Apple's attempts to block data tracking as you travel around the web could have a real impact on companies that rely on your personal information to make their billions.

asking the people that working in adtech, cross-device usage prediction and the likes: do you actually think it will disrupt your business or there are always workarounds and are relatively chill about it?

the logo is pretty forgettable, but on the bright side - at page 24 of the PDF they announced that Go 2.0 will have generics

while it's true that usually, you need to understand the basics of CS to write good functional code, we've often found that that doesn't need to be 100% correct.

we've placed a good amount of functional engineers from a Math, Physics, Logic sometimes even Biology background that had a strong affinity for functions and found OOP generally painful.

I think it's that functional programming is more of a niche with an even more disparity between demand/supply regarding the salaries.

Oh, and usually HR people have a pretty bad filter when it comes to functional engineers, so they only filter by keywords

these quotes go back as far as 2006. I'm curious whether the people above have changed their mind meanwhile?