3 ms·

Here's the reddit thread mentioned: What makes someone a bad programmer? https://www.reddit.com/r/cscareerquestions/comments/6crxwb/what_makes_someone_a_bad_p

• daxorid 9y ago
  The top comment on that post is incredibly disappointing. Unpopular though it may be, things like working memory, granular abstraction comprehension, and logical reasoning capability are highly correlated with g. And g is largely immutable under "training". Soft skills are, therefore, far more teachable than hard skills.
  • YCode 9y ago
    Maybe. I suppose it depends on the goal. From my own experience, generally the barrier for being productive at a job was soft skills, in that if a team member was suffering from an insufficient hard skill but had good people skills/personality traits I could teach them enough of the hard stuff they are missing so they can be productive, but the inverse has rarely proved true. Now, you can work around a team member's deficiencies in soft skills, but the difference is they aren't likely to pick them up.
• shagie 9y ago
  I would go with "not following the advice of how to be a programmer ( https://github.com/braydie/HowToBeAProgrammer/blob/master/README.md https://github.com/braydie/HowToBeAProgrammer/blob/master/RE... ) for your given skill level. There are soft skills and hard skills that are necessary as one progresses. Things like "know when to go home" are incredibly important for programmers who would otherwise spend days in the office (cot under the desk, showers the coworkers are lucky) given the chance.
• deleted 9y ago
  [deleted]