Re:Explain the first 10 lines of Twitter's source code to me
by pythonaut_16 on Saturday February 26, 2022 @12:35AM
(#30475417)
How to change meta tags:
1. What is the current general standard. 2. Does our site do what we want it to do? -> Yes? Then we don't need more meta tags. -> No? Go to 3. 3. Are meta tags part of how to accomplish what we want? -> Yes? Look up the docs and tags needed and implement. -> No? Implement without touching the meta tags of the doc.
That's why focusing on the first 10 lines isn't very helpful IMO. Most of these are things that are trivial to look up and read the docs on when they become necessary.
If you want to interview around a site's source you'd be better served to have a discussion around the whole document.
Re:Explain the first 10 lines of Twitter's source code to me
by withinboredom on Friday February 25, 2022 @09:10PM
(#30474696)
Their answer should include googling the latest accepted specification if they’re going to be making changes or creating new ones from scratch. If their answer is to go to stack overflow, you might have a problem.
Through the eyes of the interviewer, you googling those tags means you don't know what they do. If you were hired and for some reason had to change those tags, what is the chance that you'll just google and copy/paste? (again, through the eyes of the interviewer)
To be fair, not all people work the same way. Some are happy to swim through the mountain of knowledge that web development has become these days, others are happier specializing in a subset of web development, and others will prefer to diversify their knowledge outside of web development, which means wider breadth in exchange for lesser depth. The interviewed should make sure to clearly transmit how he works, so the interviewer doesn't have to make too many assumptions.