What a Developer Needs ?

[jk chan]

Hi Everybody Is anyone thinking abt qualtites a developer requires ? :confused: Do reply Thanks & Regards Krishnadevan.K If u can Dream... U can do it

[sreejith ss nair]

hi, It's purly depend on company where you working for.;) ************************** S r e e j i t h N a i r **************************

[Anonymous]

After all one should have his principles and aims .. ok ?:cool:

[toxcct]

a computer... is that correct ? :-D:laugh:

---

TOXCCT >>> GEII power

[sreejith ss nair]

The answer that you mentioned is not a quality that a developer want. But it is the basic requirement to achive and impliment his (developers) first vision about the software. Sreejith Nair [ My Articles ]

[toxcct]

oh, i see you don't have any sense of humour... sorry for you bye

---

TOXCCT >>> GEII power

[sreejith ss nair]

No. I have good sence of humor like you. But we must be very clear about where we need to apply this. I thing lounge is the place where we can discuss sence and humor. That is sence of humor. :-D Sreejith Nair [ My Articles ]

[Al Gardner]

The ideal programmer, - Needs to play with things, to see how they work and produce a RAD prototype as proof of concept - Needs discipline, to take what they have just worked on and throw it away, learning from its lessons but not taking its structure forward. - Needs to think the entire design through, not just start coding. Produce a design that covers everything for the version one product and provides support for future enhancements. - Needs a thick skin, to take criticism as people pick holes in the design. - Needs to avoid a big ego, so that good suggestions made by other people, are integrated into the project in place of your own. - Needs to consider reuse. "Has somebody already done something that I can use, Or can I make this slightly bigger so I can reuse it in the future" - Needs to work as part of a team, so that they communicate what they are doing not just stick their head in the sandbox. Try and keep abreast of what others are doing. You might find some of your work overlaps with other team members and both of you can benefit. - Needs to test everything. At least three times. Pick stuff that should work, stuff that shouldn't work and something else for good luck. - Needs to understand that the GoalPosts will have moved. e.g. The User/Client has specced v1.0. We spend 6 months writing v1. The user now wants v2 / v1 doesn't have anywhere near the functionality the user needs. We still release v1. - Needs to constantly keep re-evaluating the design and the product, to see of any of the above can be utilised. The Real world Programmer, - Needs to understand deadlines. They can't have time to program for reuse, but they can reuse others work. They tend to keep their head down while working busily, concentrating on their own problems. - Wants the best software release they can. They will often raise issues when v1 is released and it wont meet the users real needs, although it meets the specification. Anyone else anymore?

[Gammill]

A real answer -- the guy asked a real question and deserves real answers. I have solved far more problems via tenacity than inspiration. So -- a developer needs to be able to stick to a problem. He needs patience too. (A little bit of inspiration never hurts ;P).) He must be a problem solver. He is unlikely to be a good manager of people. He must be able to work long hours with only a computer. But he must no be antisocial. He is likely to like to solve mazes. ;P He must be able to read. And read well. And he must be willing to research. There is so much to be read, studied and research! And he must be self motivated to do the research on his own. It would be nice if he can type ;P -- really -- I have known a those that could not type that pecked their code. The preceding answer hit it true that he must be able to go down a path and accept it that he went the wrong way; take what he did as a learning experience and start a new solution. He must realize that there is very rearly only one solution. Rather there's almost always a better way or at least another way. And he must be willing to admit when he has chosen the poor way. He must be willing to move on, not try for perfection; but get the job done. Done right; but not necessarily perfect. (I have seen a programmer waste lots of time to create an elegant solution to a problem that could be solved with a few more lines of code that he feels is necessary.) I hope these help -- the MOST important attribute (as far as I am concerned) is that he be: tenacious. WedgeSoft