Comments URL: https://news.ycombinator.com/item?id=47584679

Points: 6

# Comments: 0

Comments URL: https://news.ycombinator.com/item?id=47085900

Points: 2

# Comments: 0

Comments URL: https://news.ycombinator.com/item?id=46943327

Points: 2

# Comments: 0

Comments URL: https://news.ycombinator.com/item?id=46943321

Points: 2

# Comments: 2

- some are completely and utterly incompetent (they can't write a line of code at all)

- some write some code but it's just bad quality or they are incredibly slow

- some lack basic notions we require (e.g. don't know what a byte is)

- some blatantly cheat with ChatGPT or other tools

- some rage quit ("how dare you ask me to code")

- some fall into deep rabbit holes, overthink everything and make a mess

On the other hand the people that pass:

- all of them solve this in half the time we give

- even if they are nervous

In other words there's a chasm between the hires and no hires. Assuming that this interview only measures nervousness is a completely wrong notion.

BTW if you are interested in helping us transitioning the world from fossil to renewables, we are hiring: https://jobs.intellisync.it/

It's not only the sound, it's the sound, the bounce, the response to different strengths, the smell, the color. Humans are multimodal, machines are not, yet.

The moment we have a Michelin star level robot cook, then we can start thinking about automating this kind of stuff. For now, we have better results with humans!

Italians have absolutely zero problems replacing manual processes with technology. Creating each wheel is more science than art, everything is done in highly sterilized environments with exact temperature control, as an example.

F# has many theoretical qualities, which make it fun if you like these things, but it also has some fundamental flaws, which is why it's not getting a wide professional adoption.

- the build system was a mess last I checked (slow, peculiar)

- syntax is not c-like or python-like (a big deal for a lot of people)

- you can't hire developers who know it (and certainly the few are not cheap)

- the community is a bit weird/obsessed/evangelizing (a turn off in a professional environment)

- it's clearly a second class citizen in the .net world (when stuff breaks, good luck getting support)

On the other hand

- it has discriminated unions

- units

- etc.

but do you need this stuff (not want: need)? most people don't.

A better graph would be of the number of people who self-report as being employed as software developer. I doubt that would show the same decline--there have not been many stories of people abandoning the profession because they could not find employment...

1. VSCode uses SSH (with its security profile) and the user can't do anything more with VSCode that they can already do with SSH. If the comparison is between a system without SSH and a system with VSCode and SSH--sure--I understand the concern, but it's an issue with enabling SSH and not VSCode.

2. VSCode can change files and persist? Well, it's a local editor, so yeah, it can change files and persist, that's literally its purpose. If that's an issue, disable editing permissions for the user.

Of course, I can be totally wrong but I've seen these things happen (I've been both a mod and a core dev at Stack closely working with the community team 8 years ago)

Comments URL: https://news.ycombinator.com/item?id=42548156

Points: 6

# Comments: 1

In reality most candidate are just bad at estimating their own skills (in both directions) and of course they know almost nothing about the match between the skills and the position.

- the candidate has a range of salary they expect or need

- the company has a range of salaries that they can pay

If these don't overlap there's no point going forward unless the range of the company is higher.

If these do overlap, it's worthwhile proceeding. Then it's a matter of skill. If you apply and ask for the top range in my salary band, and you are truly exceptional, I'll do my best to match it. But the ask needs to be commensurate to the skills you demonstrate in the interviews. The higher the ask, the stricter the criteria to match.

If you get to the end of the process without disclosing the salary, and you pass all interviews, I'll offer you for what I think you are worth. If you have an ask and did not disclose it, you might have just wasted everybody's time.

Believe it or not, negotiating a salary higher than your worth is a terrible idea. It might sound good, but it sets you up for failure.

It achieves only making queries much harder and much more opaque. It completely fails at that.

But then, you know, I don't involve 100k people in my projects...

There's the not-so-common case of needing database independence as well, but at that point DB perf becomes a really hard problem to solve generally...

Vocalizing primes? Maybe it could be used in speech synthesis although I'm not sure that the terms allow it or that the participants would be happy with their voice becoming AI...