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.
- 7The person who wrote this "matrix" is mostly trying to brag about himself and declare that everyone else should be just like him.chrisaycock– chrisaycock2010-12-12 07:44:21 +00:00Commented Dec 12, 2010 at 7:44
- Seems interesting though. +1nayan– nayan2010-12-12 10:46:51 +00:00Commented Dec 12, 2010 at 10:46
- 2@chrisaycock: I totally agree. Much of the matrix suggests that the author has quite a narrow perspective on the subject. Many things are arbitrary, subjective and highly disputable, quite a few criterea are missing and those present are not weighted, which renders the whole thing quite useless.back2dos– back2dos2010-12-12 17:09:15 +00:00Commented Dec 12, 2010 at 17:09
- 3@chrisaycock @back2dos: Personally, I think it is an excellent list that covers most salient points of software engineering. If he himself knows all this stuff and declares that other programmers should know at least as much, then I think he is quite justified. All items are weighted, from level 0-3, there is no attempt to weight one facet of knowledge against another as all may be required, which come to the fore in a particular instance varies by instance.Orbling– Orbling2010-12-12 18:43:42 +00:00Commented Dec 12, 2010 at 18:43
- @chrisaycock @back2dos - Any rubric for measuring what people can do will be flawed, but this one is pretty reasonable. I've always measured developers against something like this list, not always expecting people to excel in all areas (depends on what you're experience and focus is).Bruce Alderson– Bruce Alderson2010-12-12 19:08:35 +00:00Commented Dec 12, 2010 at 19:08
| Show 1 more comment
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