now a funny thing that happened to me a few weeks ago:

a recruiter contacted me on linkedin... wait, don't laugh yet, that's not the whole joke (this time)...

...asking whether I'm interested in something, I was like yeah, but I'm looking for part-time because i'd like to not have a mental breakdown after 6 months this time...

her response: "well... I don't have any part-times, but I have an almost part-time..."

" 'almost part-time'? first time I've heard that phrase, what exactly does that mean?"

"it means about 160 hours"

... i sit in confused silence for a bit, then write back as I calculate: "i'm assuming you mean 160 hours a month, which is 40 hours a week, which is 8 hours a day, which is full-time. please point out where am I mistaken."

recruiter: * crickets *

Do technical recruiters think that developers memorize the technical definitions by heart instead of using them in a seamless way?

What do they want? A dev who knows how to memorize or the one who knows how to implement.

I am really angry and i feel so uncomfortable when they ask me about a specific question and consider it wrong when they don't receive exactly the same answer.

Like one the recruiter told me: well how are you expecting from me to accept you as a developer while you don't know the definition of "technical term".

Dude i learned the hard way by building projects, watching videos, implementation, analysis. I am not going to read 70000 pages to understand the root of a coding language.

You fuckin need the output so focus on this shit.

Damn i feel so angry. Sorry in advance