Skip to main content
Software Engineering

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*

7
  • 2
    Perhaps. But design skills are not that far away, even when first starting out; and people skills are valuable, irrespective of your coding ability. Commented Aug 23, 2013 at 16:59
  • @RobertHarvey Yes, but Jeff Atwood's article seems to be more about problem solving and stepping away from the computer to think about what you are programming. Commented Aug 23, 2013 at 17:02
  • 2
    @KoreyHinton Which is something that it would be entirely appropriate for someone to do when solving their very first programming problem. You can and should be doing that from day one, not once you're already proficient, that's what Robert's saying. Commented Aug 23, 2013 at 17:07
  • 1
    @KoreyHinton Which is why nobody (neither article, nor any of the people answering here) are saying you should be doing just one or the other. They're saying it's important to do lots of both, because the skills complement each other. Commented Aug 23, 2013 at 17:33
  • 1
    @Wronski I think Robert is arguing the opposite point that non-programming skills can be learned while first learning programming. I agree with this as well, but I'm glad that I personally didn't over-complicate the learning process at the beginning. My focus was like you mentioned prioritized with programming skills first, thinking skills second and now I am constantly striving to improve both. Commented Aug 26, 2013 at 22:36