Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Added the doctype vs DOCTYPE question #310

Closed
wants to merge 1 commit into from

Conversation

phanan
Copy link

@phanan phanan commented Jul 13, 2015

Do you write <!doctype html> or <!DOCTYPE html>? Explain your choice.

This question is inspired by a very interesting discussion in h5bp/html5-boilerplate, which some of you guys here are a part of. While it may sound tricky and/or nit-picky, being able to explain such a choice will say a lot about the candidate.

@arthurvr
Copy link
Member

Nah. I'm 👎. At a boilerplate it made sense to discuss this, because it's a boilerplate, but it's super nitpicky and people should not waste time discussing something like this.

Both options don't have important adventages/disadventages, it's just a code style decision. Just like we don't ask people if they write function () {} or function() {}.

@phanan
Copy link
Author

phanan commented Jul 20, 2015

While I agree on this:

At a boilerplate it made sense to discuss this, because it's a boilerplate, but it's super nitpicky and people should not waste time discussing something like this.

This

Both options don't have important adventages/disadventages, it's just a code style decision. Just like we don't ask people if they write function () {} or function() {}.

isn't exactly the same with what I had in mind when proposing this question. True, no style has more important (dis)advantages than the other, but the question should give the interviewee a good chance to show off their knowledge/skill (compression? consistency? IDE compatibility?)

Anyway, again, I'd agree on your first point.

@phanan phanan deleted the doctypeDOCTYPE branch March 17, 2016 01:43
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants