Why React uses className? | 2023 React Interview Questions and Answers 

Still a useless question and knowing the answer to the question doesn't make you a better dev ..

Personally, I have not met many devs that can give decent interviews. It is truly a skill that relies on a lot of intuition. Presumably there is a massive associated cost to losing leads and interviewing in a negligent manner; Both when the talent pool is shallow or deep. I get that this is more about the why, rather than the answer, and I can get behind that with the understanding that if an applicant answered this to this level of correctness, I could care less. One should be cautious though, as you have to be careful with open ended questions as you are possibly setting the interviewee up for failure - especially with exceptional talent. The Dunning-Kruger effect can easily siderail any effort in gauging acumen in such a short window. In fact, the dealing with DKE in interviews would make for an exceptional video for senior+ developers. Back to the point, If the conversation becomes frustrating to you or the interviewee, or leaves you without enough technical insight, you may have just failed as an interviewer. Sure, the interviewee may have failed miserably either way, but environment is everything. That said, I think this is a banger of a video and it really got some great conversation going. Good work!

Subscribed mate! Please continue doing what you are doing, it's great 👍

Thank you! Welcome aboard! 🙌

It's my pleasure, thank you ❤

Thank you very much! I'm experimenting with shorts on RU-vid, but to be honest I don't feel it very well right now. I always catch myself trying to say more that I can in those 60 seconds. It's very limiting for a content if you want to dive deep and actually explain something, not just show that it works. But who knows, maybe I'll find a way.

That kind of content is for people who don't wanna put the time to actually learn something. Screw 'em

Facebook openly acknowledged they lost 60billion trying to push short form content, it's empty calories, you're right to follow your gut. Not all advice is informed advice kids.

It seems like your ask has been successful 😅 Thanks!

Thanks! Glad you enjoyed it!

Hey, thanks so much, means a lot! I see this question is popping up a lot, so I'll try to refer to it in a separate comment at the top.

Exactly! Good description for that

Thank you! Nice to meet a fellow sould, who likes the "how" 😄 I'll try to keep it up! Unfortunately, I don't have a blog. Actually it's the first instance of me publishing anything, so now I'm just focusing on creating some consistency here. But maybe in the future I'll try with a blog, or maybe twitter (sorry, X :D) account.

Dziękuję ! 🙂

Totally agree

Thank you! It already made a huge jump since your comment, but I appreciate it

Hey, exactly. It's just an extra note that you can make. Not directly related to the problem that "className" itself solves.

Hey, sure thing! :) www.npmjs.com/package/classnames www.npmjs.com/package/clsx

Hey, not sure what exactly you are asking about, but the general idea from the video was that you can simply use aria and data attributes in JSX and it will be passed down to the DOM by React. So you don't have to worry that React has a different names for them. But, if you want more to know more about these attributes in general, for now I can link some nice resources: Data attributes: css-tricks.com/a-complete-guide-to-data-attributes/ Aria attributes: web.dev/learn/accessibility/aria-html/

@@UIEngineering thanks man. I don't know what these aria or data attributes do. I was hoping of could make a tutorial on these.

​@@FzsHotDogInDonut Sure! I'll add it to my bucket list, but can't promise anything. I hope those links will help in a meantime though 🙂

Oh yeah, thanks, that's what I meant 😊

You might want to hold yourself back😅 What if you are asked about it as a side question, during a coding challenge? Like: "BTW do you know why you have to use className instead of a class?"

​@@UIEngineeringthen they can have a conversation, but it's hard to see how this question assesses an applicant's capabilities

@@HiYesThisIsJakeshouldn’t you know what reserved keywords your language has and what the rules are around them? What’s a better question in your opinion?

@@0oShwavyo0 if you want to test that knowledge, then you can ask about it directly instead. This question doesn't test that -- this question just happens to have a wrong answer relating to keywords.

@@HiYesThisIsJake not at all, the destructuring argument is directly a result of it being a reserved keyword.

No offense, but he seems like the engineer to ask someone this sort of gotcha question. Also, the whole React and Next ecosystem is big pile of shit. You would need PHD in both these topic if you want to build something useful compared to other frameworks.

@@MahbuburRahman-uc7np maybe if you want to use all the advanced features, but the basic react docs and excellent and easy for a beginner to pick up. Overall its a straightforward, highly documented, and highly used framework, so really its perfect for a beginner

Hey @edgay, thanks for the comment. And yeah, you would be surprised. From my experience, it is actually VERY common to get questions that don't test any particular skill in practice, but rather an overall understanding of the ecosystem. Especially for mid/senior positions, it's interesting to test if a candidate has a deeper understanding of some nuances that come with the tools they are using, and if they are able to paint a bigger picture and articulate it well. For me personally, every question is just an opportunity to show my interest in the topic and how many exciting things can hide behind a seemingly easy question. And of course, don't take this video as the only definitive answer that you have to follow exactly. I remember being asked if React is a library or framework in one of my interviews. I didn't agree with the interviewer (sic!), but I showed that I have broad knowledge and some good arguments too, and I got the job ;)

@MahbuburRahman-uc7np none taken. But take into account everything stated above, that it is not with a mindset of "there is only a one good answer", and it's definietely not a "gotcha" question that aims to just "catch" you at not knowing something. I wouldn't call the whole ecosystem a pile of shit. I think there is a sentiment that the frontend became a place where a lot of things are overengineered, but really it's just a complexity that comes with Web becoming the biggest software platform of modern times. How many apps we had 20 years ago? How many apps we use by accessing them through a browser today? But I do think that React is very resource-hungry and I am a skeptic in terms of moving everything to SSR. The whole environment is changing rapidly, but I think it's exciting :)

It's not always, but such questions come sometimes. For a junior dev possition should be more important how than why imo, but still happns and anyway a very nice to know. Comming from a how > why perso