You are not logged in. Your edit will be placed in a queue until it is peer reviewed.
We welcome edits that make the post easier to understand and more valuable for readers. Because community members review edits, please try to make the post substantially better than how you found it, for example, by fixing grammar or adding additional resources and hyperlinks.
-
4So in your mind there is no room for someone just being approximate about it because they don't want to waste space having another mark up language section? To me that's pedantry way beyond what's useful.Jon Hopkins– Jon Hopkins2010-12-20 12:08:05 +00:00Commented Dec 20, 2010 at 12:08
-
1+1 when i see a CV with HTML/CSS under 'programming', i read no further. either he doesn't know the difference (so he's no use for me), or hopes I don't know the difference (so i don't want to work with him)Javier– Javier2010-12-20 14:22:47 +00:00Commented Dec 20, 2010 at 14:22
-
2@Jon Hopkins: Attention to detail is a necessary quality in a programmer. Putting HTML under programming languages is not being approximate, it is being sloppy. That makes a very bad first impression if you are applying for a job as a programmer.Dima– Dima2010-12-20 17:03:50 +00:00Commented Dec 20, 2010 at 17:03
-
1@Dima: absolutely. informality is ok, sometimes even in writing, imprecision in the very basic concepts of trade is unacceptable.Javier– Javier2010-12-20 18:09:37 +00:00Commented Dec 20, 2010 at 18:09
-
1This is ridiculous. Resumes and interviews are one of the most problematic parts of our industry right now. You never know if someone who knows the difference still puts "HTML" under "Programming Languages" because they are scared some HR drone won't notice it under "markup/design/etc" and kicks out their resume. You should at least call them up or bring them in. If they tell you to your face that they "program in HTML," well... that's really a red flag. But then again, think of what you can accomplish now in HTML 5 alone! Is it really such a stretch?GHP– GHP2011-08-12 14:04:09 +00:00Commented Aug 12, 2011 at 14:04
|
Show 5 more comments
How to Edit
- Correct minor typos or mistakes
- Clarify meaning without changing it
- Add related resources or links
- Always respect the author’s intent
- Don’t use edits to reply to the author
How to Format
-
create code fences with backticks ` or tildes ~
```
like so
``` -
add language identifier to highlight code
```python
def function(foo):
print(foo)
``` - put returns between paragraphs
- for linebreak add 2 spaces at end
- _italic_ or **bold**
- indent code by 4 spaces
- backtick escapes
`like _so_` - quote by placing > at start of line
- to make links (use https whenever possible)
<https://example.com>[example](https://example.com)<a href="https://example.com">example</a>
How to Tag
A tag is a keyword or label that categorizes your question with other, similar questions. Choose one or more (up to 5) tags that will help answerers to find and interpret your question.
- complete the sentence: my question is about...
- use tags that describe things or concepts that are essential, not incidental to your question
- favor using existing popular tags
- read the descriptions that appear below the tag
If your question is primarily about a topic for which you can't find a tag:
- combine multiple words into single-words with hyphens (e.g. design-patterns), up to a maximum of 35 characters
- creating new tags is a privilege; if you can't yet create a tag you need, then post this question without it, then ask the community to create it for you