Preparing a Michelin star worthy meal is orders of magnitude harder than checking a cheese for defects.
It requires the same basic modality
Readit Newssklivvz1971 commented on Why Tap a Wheel of Cheese? cheeseprofessor.com/blog/... · Posted by u/speckx
sklivvz1971 commented on Why Tap a Wheel of Cheese? cheeseprofessor.com/blog/... · Posted by u/speckx
- "For all their expertise, I am sure a technical solution would also easily be able to detect what they are looking for: voids within the cheese, or lack of uniform density..."
Out of pure curiosity, how would an industrial process engineer approach this problem, de novo?
It wouldn't. Not for now
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.
As a person who's worked with the author (a great guy!) and with the F# community on a very large F# project: don't bother with F#, professionally speaking.
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.
sklivvz1971 commented on Software engineering job openings hit five-year low? blog.pragmaticengineer.co... · Posted by u/m3h
I don't think this means what they think it means: a _lot_ of job postings get filled before they get counted. Think about it, there have been a lot of layoffs. Many of these people have friends that can refer them to jobs before they are posted.
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...
sklivvz1971 commented on VSCode’s SSH agent is bananas fly.io/blog/vscode-ssh-wt... · Posted by u/zdyxry
I am very confused by this post:
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.
sklivvz1971 commented on Luigi Mangione's account has been renamed on Stack Overflow substack.evancarroll.com/... · Posted by u/OsrsNeedsf2P
Just a hunch that this could be a mistake of an overzealous community mod that thought that the nick Luigi Mangione was a troll... and that Evan Carroll is the best troll on the Stack Exchange network and he pushed the situation as he does and simply had the opposite effect than he thought he would ("Evan Carroll is flamebaiting again? There's no real problem, give him one year suspension" instead of "Oi, did someone make a mistake here here?")
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)
The real important question is the subsequent one:
— What are your salary expectations?
— $X
— Ok! That means if we propose Y, would you envision it?
— Yeah, maybe, because I’m out of choice / No because I already have an offer at $X-1.
Source: I’m hiring (and yes, Y enters into consideration because most candidates overestimate their skills, but I always go for X if the candidate is as expected).
> most candidates overestimate their skills
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.
Here's the thing:
- 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.
- 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/