Link Details

I vote it down because this is yet another to-learn list without any non-technical skills. It reinforces the idea that you don't need to care for other skills, as if the role of a developer had no other requirements. The author doesn't try to demonstrate that he is not yet another monomaniac that thinks that everything must be sacrificed in order to be a better-than-average developer. This demonstration is necessary because the anxiogenic demeanor of the article is far too common. Having the enthusiasm to learn all that is one thing. Concealing this agenda with a balanced life is another that is definitely not trivial.

I agree with Dalton! I should have had some non-technical skills like communication and domain knowledge in the article and should have taken out a couple of them mentioned there. I'll have it next year :)

Hello Srikanth,

I'm here again because I've changed my mind with regard to some of my ideas. Communication, which I had previously mentioned as a non-technical skill, is actually a (very) technical one. It becomes very clear as you consider the number of books on communication theory and keynotes on the topic. Moreover, the very idea that communication is a solely personal skill seems to indicate a disconnection with other disciplines, an isolation that is a byproduct of excessive specialization - the very problem that I was complaining about in the first place.

Nevertheless, I would like to apologize for my overly critical stance. It contradicts the very point I was making about communication skills. Your graceful response, on the other hand, is a demonstration of such skill.