|
- A sense of humour
- A good nose for smells.
|
|
|
|
|
Someone who would understand "Your password is not long enough joke"
I do not fear of failure. I fear of giving up out of frustration.
|
|
|
|
|
Code smells or smells in general?
Because I have a great nose and walking through the inner city early in the morning is no picnic, I tell you
|
|
|
|
|
Developer should not be bound to any specific property, Developer Develop something and it needs Thinking, creativity, curiosity, keen, innovations, ability to understand...
***How come General business acumen helps developer to code ? (option to be removed from survey)
Find More .Net development tips at : .NET Tips
The only reason people get lost in thought is because it's unfamiliar territory.
|
|
|
|
|
Just to respond to your comment on general business acumen...
Working as a consultant/business analyst/contractor, it is also important to recognize the overall business needs of the client. Having some level of business understanding and acumen helps in making design decisions with the client, or at least recognizing the clients limitations as to what can be done. We can come up with a great new system for our client, but if they cannot afford all the "bells and whistles" because of resource/budget limitations we are failing our client. Thus having some level of general business knowledge can help in recognizing this, and coming up with a reasonable compromise in what needs to be rolled out in the first release, and in upcoming releases.
Also, as a consultant running my own business, it helps to have some of level of knowledge in business...
|
|
|
|
|
There are times when a problem resists resolution even after enlisting the help of others. At these times tenacity and dogged determination eventually drive you to a solution.
|
|
|
|
|
I think this is the only reason I'm still a coder. I'm too stubborn to quit / admit defeat.
|
|
|
|
|
Adding to this, the real gift is the ability to let go of the difficult problem enough to come up with "novel" solutions, like:
- FastBack: Don't let the floppy drive spin down (drastic reduction in backup times)
- NCD: Store the directory structure in a file for quick referencing
- Tape Error: Realizing that we did not have to do more than 6 lines of code to handle a tape error during an update, because we could actually just skip all "deletes" (missing records) until we got our first add/update (meaning we resynched naturally).
- Modified Binary search to find the "First" item in list with duplicates (fun/easy problem)
That is what is truly amazing. Twisting a problem (Binary search) into a solution that creates a better solution than originally intended.
There seems to be a "tipping point" where every obvious solution to a problem is UGLY, until a viola!
|
|
|
|
|
I think I get stuck in the "ugly" stage - heard-headedness + OCD is not fun at all
But yes, when you can push through it becomes a thing of beauty
|
|
|
|
|
|
S.. as a Service, Yes!
|
|
|
|
|
You forgot an option:
a good vocabulary in swearing (at your computer)
|
|
|
|
|
At the end of the day, we are paid to solve problems and deliver. Everything else is means to that end.
|
|
|
|
|
Right. And the question is which of those means are important to achieving any given end (multiple choice).
|
|
|
|
|
The skills needed to be a web developer and the skills needed to write a compiler are vastly different, and so therefore you would expect the skills to likewise differ too. To lump the skills for every developer into one big melting pot therefore doesn't work. Whilst there are skills that are common to both, there are also skills that fit more readily to one role than another.
"There are two ways of constructing a software design: One way is to make it so simple that there are obviously no deficiencies, and the other way is to make it so complicated that there are no obvious deficiencies. The first method is far more difficult." - C.A.R. Hoare
Home | LinkedIn | Google+ | Twitter
|
|
|
|
|
I think your core "basic" developer traits will suit you well no matter what niche you end up in, the same can be said of the opposite, as well. If you suck...you suck.
|
|
|
|
|
I agree that some traits are transferable across development disciplines, but certain traits are more applicable than others. Creativity for example is (arguably) more useful to a web developer than perhaps a compiler writer.
"There are two ways of constructing a software design: One way is to make it so simple that there are obviously no deficiencies, and the other way is to make it so complicated that there are no obvious deficiencies. The first method is far more difficult." - C.A.R. Hoare
Home | LinkedIn | Google+ | Twitter
|
|
|
|
|
That's completely dependent on how you define "creativity", I personally don't limit it to the artistic aspects of page layout or UI development.
In my opinion creativity is one of the key aspects to being a good software developer.
|
|
|
|
|
|
Same here, I feel you need all of the above to a damn good one. Else you wither away and DIE!!!
|
|
|
|
|
Don't forget common "logic". Meaning: be able to order the steps of a solution and do the first step before the second step. And be able to see the difference between cause and consequence.
That may be part of "intelligence" or "problem solving capability", but need not be.
|
|
|
|
|
Going into the detail would take pages, but, in fact, what you're saying isn't always true.
I was working on work-flow management and set it up for a purely data-driven methodology. It would deliver work to a persons desk when the information necessary & sufficient to do it was available.
It turns out, when done correctly, that one needs not give any order to any steps in a process. The availability of data does that for your - and process can run in parallel, sequentially, or whatever without any problem. New steps are automatically in their right position based upon nothing more than their data requirements.
Even the order of doing work is an abstraction that need not be define beyond "do it when you can - and not before".
"The difference between genius and stupidity is that genius has its limits." - Albert Einstein | "As far as we know, our computer has never had an undetected error." - Weisert | "If you are searching for perfection in others, then you seek disappointment. If you are seek perfection in yourself, then you will find failure." - Balboos HaGadol Mar 2010 |
|
|
|
|
|
First you need knowledge and skill in a specific technology, or you won't be able to do anything (why wasn't that rated 5 out of 5 by everyone)?
After that it's communication. Too much bad code is written because of communication failure.
Communication, whether it's with a customer, your manager, or your coworkers, can make or break a project.
The best teams are teams that communicate.
Unfortunately, many people don't see it that way
|
|
|
|
|
Don't quite agree with you here. Every now and then I have to learn a new technologies with very little time to do so. To me, being able to learn something very fast is key. Having prior knowledge of a technology is an advantage, not a requirement. (Check the next software development job that is posted on you intranet)
"Program testing can be used to show the presence of bugs, but never to show their absence."
<< please vote!! >></div>
|
|
|
|
|
I never said learning something quick isn't important (I rated it 4/5).
But when a team communicates you may find that learning goes even quicker.
Development is more streamlined.
Specs are clear (or at least you're clear on what's unclear).
You can't build awesome applications by "quickly learning a language" though, intimate knowledge is required.
|
|
|
|