Live data from Hacker News

We created a fake language to root out resume liars

facebook.com

321–330 of 771 posts

Re: We created a fake language to root out resume liars

#321

Earlier quoted context omitted.

See https://en.wikipedia.org/wiki/Law_of_Jante#Definition

That has a strong Fightclub vibe.

The 12th law of Jante is that you are not to think you are good enough to change the laws of Jante.

Re: We created a fake language to root out resume liars

#322

Earlier quoted context omitted.

Does it? If someone from legal reads the contract, why would they bother dealing with this gimmicky clause? The budget has already been approved and sending someone a plant might cost another 30min of their time they rather spent on doing their job.

"I can think of a hypothetical reason why you might be wrong in very specific circumstances, so I'll suggest that could be a reason why the general case is wrong" is such a dumb argument. Obviously there might be occasions where a client reads the clause and chooses to ignore it. Very rarely, someone in legal might decide to ignore the clause because they're a bit lazy and don't care about saving their employer some…

Fair enough. My experience is limited to large corporations with bloated, slow procurement processes. So I would be really surprised if legal would get back to me about something like this. That said, I don't think I've ever encoutered these type of jokes.

Re: We created a fake language to root out resume liars

#323
post #264

Earlier quoted context omitted.

I've heard hiring is not a cheap process. That must have been a critical skill if you chose to restart the process.

Not necessarily. It might not be about the lack of the particular skill they lied about, but the fact that they lied at all and what that indicates about them as a person/employee.

If you fired everyone who ever lied you'd have nobody in your company.

Re: We created a fake language to root out resume liars

#324

Earlier quoted context omitted.

Honestly, the thing I hate the most about IT is how bad it is while no one admits to it. These are problems I've encountered at several companies: * No budget for tooling. Be that software outside the ide or be it for hardware. * Cargo cult is so much bigger than anyone will ever admit. * The lack of caring about other departments. We're a team and we need to work as a team so the company can make money to pay our sa…

> The amount of people who don't know what they're doing. So many people seem to have 1-year * x experience. They reach a certain level and they just stop. Part of the problem is because people only look at years of experience at all, and recruitment often inflates the requirements. I don't need 5 years of work experience in .NET to modify an existing application with very defined and clear boundaries: within a few m…

The biggest problem is that there is no baseline of competency. Seriously, when somebody asks for minimally passable competency for employment as a software developer what do you point to in 5 words of less? Software doesn't have that so instead you get a bunch of posturing and smoke signals. Seriously think about how you would explain this to your non-developer uncle who is an educated professional of any other industry.

Think about it like this:

What is the minimal passable qualifier to be a lawyer: a law license. What is the minimal passable qualifier to be a truck driver: a CDL. It is illegal to do those, and many other, jobs without the minimum qualifier.

Worse is this tooling bullshit. No carpenter or mechanic creates a resume detailing their job experience using a screw driver or a hammer. Those are just assumed. If a candidate felt the need to mention stupidity like that you don't hire them. For some reason software has that backwards which invites and encourages incompetent people to apply and degrades competent people to compete with unnecessary stupidity.

Re: We created a fake language to root out resume liars

#326
post #316

Until recently I was never part of the hiring process at any company because I was simply too new. I always thought how it was insane that people would say "I only spend 30 seconds on each resume", that I would somehow be better and do a more thoughtful analysis of the candidate. Boy was I wrong, the amount of resume you can get for a job is crazy and most candidates are absolutely not a good fit. I even had one pers…

Or they (or a recruiter) sent in an old resume...

Re: We created a fake language to root out resume liars

#327
post #298

Earlier quoted context omitted.

No, in practice it is мова, and modern standard Ukrainian mainly uses inherited Common Slavonic *językŭ ‘tongue (organ); language’ only in its meaning ‘tongue’. The article for "Ukrainian language" at the Ukrainian Wikipedia is literally "Українська мова" [0] [0] https://uk.wikipedia.org/wiki/%D0%A3%D0%BA%D1%80%D0%B0%D1%97...

So in guessing ова is pronounced ova?

The letters correspond. From the perspective of Russian, you can't know the pronunciation without knowing which syllable is stressed. Ова will be pronounced "ova" if the first syllable is stressed, but "ava" if the second is.

Most modern-day approaches to spelling foreign words aren't concerned with whether the spelling suggests anything close to the correct pronunciation. They concern themselves more, as here, with whether there is a system that suggests an "official" spelling.

Compare how Chinese immigrants in the 19th century might get names like 王 Wong, 李 Lee, or 魯 Loo, whereas Chinese immigrants today have names like 王 Wang, 李 Li, or 鲁 Lu.

Re: We created a fake language to root out resume liars

#328
post #297

Earlier quoted context omitted.

>I've been to plenty of interviews where my CV hasn't been given more than a glance. I have a fake programming language on my resume, has been there for years. To top it off, I used a well known video game cheat code. I've been hired several times with that on my resume, so far no one has ever mentioned it.

There are so many programming languages out there, as a hiring manager it’s not uncommon for me to see resumes with languages I’ve never heard of and probably don’t care much about. The cheat code just depends on how it has been inserted into the resume. If I threw out every resume with some weird quirk, spelling or grammar issue, layout problem, etc. I’d probably never hire anyone

> some weird quirk, spelling or grammar issue, layout problem

I don't dock points for layout issues (unless they say they have experience in front-end work...), but spelling and grammar is exactly what you should be getting right in an resume. I don't meant to say I would be unreasonable pedant about the use of prepositions, and I'd probably overlook an MS Office autocorrect (like how Excel always changes "HSA" to "HAS", grrr) - and small mistakes must never invalidate someone immediately - but it means I'm going to be in the session with a dim view of the candidate until and unless they demonstrate otherwise.

That said, recruiters and agencies do edit resumes - so if something seems off with a resume (e.g. "20 years experience with Rust") then I do have a policy of directly contacting the candidate with the resume attached and asking them to verify that this is the resume they wrote. It's also why I sign my own resume PDF with my AATL certificate and mention that fact when I get to contact the hiring manager (e.g. "oh hey, did you have a chance review my signed resume? if it wasn't a signed PDF please let me know, thanks!)

Re: We created a fake language to root out resume liars

#329

Earlier quoted context omitted.

What about all the different types of diagrams? Use cases, activity diagrams, deployment diagrams etc. Yeah - 'informal' UML use a lot of people are happy with but some things like exactly what some of the features of activity diagrams mean is amazingly badly understood by a lot of people. I'm ok with the 'UML as sketch' approach, but 'UML as blueprint' is a nightmare that I've never seen work: https://martinfowler.c…

Honestly, most of the time I use these diagrams just to give people the gist of what I'm talking about. And my diagrams are super low effort. Think low effort whiteboard diagrams during a meeting style. > Yeah - 'informal' UML use a lot of people are happy with but some things like exactly what some of the features of activity diagrams mean is amazingly badly understood by a lot of people. I'm talking super basic stu…

Same with frontend, I give a very rough wireframe trying to translate wtf they are telling me. The end result usually looks very different because once you flesh stuff out IRL there is always a bunch of hills to climb that were unanticipated. And that’s why it always takes 2-3x longer than we first thought.

Especially in a large application with lots of moving and breakable critical parts.

The only solution is constant feedback loops and not being bummed out when your code goes in the dustbin.

Re: We created a fake language to root out resume liars

#330
Dealing with applicants who don't know what they are doing is hard, but trying to trick people is disingenuous and I personally would avoid any application that involves any trickery.

Also sometimes an internal or esoteric tool gets listed in the application, you never really know! The people who write the job description also sometimes make typos and mistakes.

Post reply on HN