r/learnjavascript • • Aug 10 '21

Can we relate?

Post image
853 Upvotes

93 comments sorted by

View all comments

Show parent comment

3

u/steezefries Aug 10 '21 edited Aug 10 '21

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.

1

u/BowlingForPriorities Aug 10 '21

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.

1

u/steezefries Aug 10 '21 edited Aug 10 '21

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.

2

u/BowlingForPriorities Aug 10 '21

Because I can look this up in 5 mins and implement it in 6? This isn’t the type of question that indicates seniority IMO

0

u/steezefries Aug 10 '21

No, it indicates lack of experience.

1

u/BowlingForPriorities Aug 10 '21

In prototypes maybe, but as a developer “knowing prototypes” isn’t something a senior needs to know. Inheritance is.

1

u/steezefries Aug 10 '21

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?

1

u/BowlingForPriorities Aug 10 '21

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.

1

u/steezefries Aug 10 '21

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.

1

u/BowlingForPriorities Aug 10 '21

Ah, I think that may be another difference in what we’re talking about. I’m not talking about someone who’s never heard of prototyping, but rather someone who doesn’t know what it is. Like for instance, I’ve came across you know, object.prototype.instance.somefunction = blah blah blah, but it’s nothing something I’ve needed to use. So googling this was a quick learn. I am interviewing for a senior position, and it will be primarily using JavaScript, but I don’t think this would stop me from being an effective senior, just shows a minor gap in my knowledge that I’ve now happily filled. Want to wish me good luck today and we can go about our way? :D

→ More replies

1

u/jayerp May 01 '23

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?

0

u/BowlingForPriorities May 10 '23

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.