Linked by MOS6510 on Sun 5th May 2013 22:43 UTC
General Development "In order to be an effective programmer, you need to possess a combination of traits that allow your skill, experience, and knowledge to produce working code. There are some technically skilled developers who will never be effective because they lack the other traits needed. Here are seven traits that are necessary to become a great programmer."
Thread beginning with comment 560646
To view parent comment, click here.
To read all comments associated with this story, please click here.
RE: Trait Zero
by Pro-Competition on Mon 6th May 2013 14:48 UTC in reply to "Trait Zero"
Member since:

Amen, I could not agree more. This is one area that really pays off.

The situations I've encountered most are either a vague, ambiguous description of what is needed, or a hacked-together requirements doc that is over-detailed in some areas but glosses over others.

If you sit down with the user to see what they are trying to do, you get a sense of their workflow, interruptions and frustrations. The details matter. (It is shocking how saving a mouse-click or two can turn "I hate it" into "I love it".)

This is also where thinking about the future comes in. Eventually you develop a "Spidey Sense" about how the program/process might evolve in the future, where you can save almost total rewrites (or a horrible mess) down the road if you put a little extra design/work in at the start.

Reply Parent Score: 5

RE[2]: Trait Zero
by hhas on Tue 7th May 2013 11:47 in reply to "RE: Trait Zero"
hhas Member since:

Amen, I could not agree more. This is one area that really pays off.

What depresses me beyond belief is that your comment and mine are the only ones on either OSNews or TechRepublic that even acknowledge the existence of a world outside The Team, never mind advocate actually interacting directly with anyone in it.

There is something terribly wrong in a mainstream programmer culture that sees the program as Everything: The End In Itself. But the program itself is nothing; it is merely a means to an end. The only thing that gives a program any purpose or value whatsoever is the people who use it.

Reply Parent Score: 4

RE[3]: Trait Zero
by Kochise on Fri 10th May 2013 07:53 in reply to "RE[2]: Trait Zero"
Kochise Member since:

Nope, it's just that management team tend to enforce isolationism of said sector. I'm a coder but I like to know how is used my code, how to improve it considering its usage, the limits of the specifications given to be coded. As an embedded coder I learned electronics to have a better symbiosis with the software I develop.

In one of my previous firm I worked for, I was in close partnership with the hotline to solve users' issues with our applications. I was bullied to keep my dedicated place and shut up. The management team thoughts they knew more about users' expectations and finally screwed everything over.

"Divide and conquer..."


Reply Parent Score: 2