[xcipher]

Hi everyone! I'm new here and this is my first thread on this forum. I hope you guys will enjoy it (I didn't wanted to create a normal hello thread).

So, my question is: 'What kind of non-programming skills are the most important for a programmer?' // both when it comes to career and programming skills development.

Can't wait to see the answers,
bart

[no2pencil]

xcipher, on 11 December 2011 - 04:55 AM, said:

So, my question is: 'What kind of non-programming skills are the most important for a programmer?' // both when it comes to career and programming skills development.

The ability to take proper documentation & to follow documentation created & presented by others.

[creativecoding]

Problem solving. The ability to overcome problems using multiple solutions, and then analyzing each solution to find what fits best.

[xcipher]

creativecoding, on 11 December 2011 - 03:02 AM, said:

Problem solving. The ability to overcome problems using multiple solutions, and then analyzing each solution to find what fits best.

So that would probably be logical thinking, I think that's what you ment.

I guess abstract thinking is really important. What do you guys think?

[lordofduct]

problem solving - the skill uses both "logical thinking" and "abstract thinking".

[jon.kiparsky]

This is part of problem-solving, but deserves a callout, since it's often neglected: the ability to listen to the person who needs the code, and understand what it is they actually need.

To solve problems effectively, you need to know what the problem actually is, and you need to isolate a useful solution. This is not something you typically have to deal with in a CS course, usually your professor will do this for you, but it's a necessary skill.

[noahgibbs]

The ability to cut down a solution to its smallest useful, implementable form. Like a Minimum Viable Product, but for stuff smaller than a product :-)

[ButchDean]

jon.kiparsky, on 12 December 2011 - 06:11 AM, said:

This is part of problem-solving, but deserves a callout, since it's often neglected: the ability to listen to the person who needs the code, and understand what it is they actually need.

To solve problems effectively, you need to know what the problem actually is, and you need to isolate a useful solution. This is not something you typically have to deal with in a CS course, usually your professor will do this for you, but it's a necessary skill.

This without a doubt!