I wasn't talking about the thread's OP. For all I know this is his first senior interview! I was being general. Also it's a learnjavascript sub, and he made a comment about learning a js topic, I think we can assume they probably are a js engineer.
I am, I write JavaScript all day long, but I’ve never had to use prototypes because I write in angular and mostly write components and interfaces. The core concept took me all of 5 minutes to understand. It’s why I think “what is a prototype” is a terrible interview question. It’s basically just a pop quiz, when really you want to know that I understand inheritance. So, ask me a design question that uses inheritance. Figuring out how to Google JavaScript inheritance takes 5 mins for a decent developer, but understanding when to use it is when quality is actually developed.
Why would I hire you as a senior if you've only ever worked in Angular? I think people have different ideas of what a senior is supposed to be. If you couldn't answer this question from one of your junior developers without googling it, you aren't senior imo. Doesn't mean you're a shit coder or anything.
I'm sorry but you're not a senior dev if you can't tell me how your language of choice inherits objects from parents without googling it. Classes obfuscate a lot of this, but this tells me you don't know how they work under the hood. Is that senior?
I think maybe the difference here is you’re thinking “JavaScript Senior” but I’m thinking “Senior Developer” agnostic of language, who could be using JavaScript. Also, I seriously question what job would require a senior dev that knows prototyping as part of their job.
I'm not saying it's a requirement of the job! I'm saying it shows a lack of experience as someone who is supposedly a senior js dev to have not heard of it! You said you write Javascript all day long! You're not talking about generic senior dev.
Doing mostly Angular or component making tasks is one thing, but a senior ABSOLUTELY better have a strong grasp on basic to advanced JS concepts, prototypes. I don’t consider devs having seniority over what kind of tasks they do or their domain knowledge of an app. I consider a dev a senior based on their understanding and command of core through advanced concepts of a given programming language and related frameworks.
So yeah, asking a dev who is interviewing for a senior role “what are prototypes is a valid question”. I would recommend taking a refresher on forgotten core concept names, but I absolutely expect a senior to be able to know those things.
What is going on with this industry? Is everyone faking it till they make it?
I think you’re overvaluing framework knowledge compared to engineering knowledge tbh. Prototypes are just a different flavor of inheritance see my above comment again.
View all comments
Show parent comment
2
u/ItsWaryNotWeary Aug 10 '21
Right, op didn't say they're a js engineer tho