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.
Required fields*
- 
        6Nah, angry birds is probably like 2 or 3 keywords repeated ad nauseum with funny photographs of birds. Yep. It's a database for ornithologists right?Jimmy Hoffa– Jimmy Hoffa2013-08-23 17:24:40 +00:00Commented Aug 23, 2013 at 17:24
- 
        Well, but in certain way Peter Norving's point refer to the fact of "mastering" not knowing in a superficial way (that is the central point of his article) the programming language. In fact, Peter and Jeff Atwood refers to be a "master". As the same way you describe Jeff Atwood posture I describe that Peter Norving is saying that being an excellent programmer requires a lot of coding (with the implicit learning topics) and practice.PlainOldProgrammer– PlainOldProgrammer2013-08-24 06:08:10 +00:00Commented Aug 24, 2013 at 6:08
- 
        2@Wronski: Ah, you're back, I see! Nice to see you again. While you were away, we were discussing your question, closing it, and reopening it. Anyway, so what are you saying, exactly? Peter Norving's point is that you can't be a master in 24 hours, or even 21 days. Jeff Atwood's point is that you can't be a master by only writing code. They are both right.Robert Harvey– Robert Harvey2013-08-24 06:12:14 +00:00Commented Aug 24, 2013 at 6:12
- 
        1@Wronski: Masters are both good coders and good engineers.Robert Harvey– Robert Harvey2013-08-24 06:22:57 +00:00Commented Aug 24, 2013 at 6:22
- 
        3@RobertHarvey After 11 years later I totally understand the point, and now is ingrained in me! ThanksPlainOldProgrammer– PlainOldProgrammer2025-02-22 05:50:17 +00:00Commented Feb 22 at 5:50
                    
                        
                    
                 | 
            
                Show 3 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