|
People with less intelligence wont even try to be a developer, they would instead stick to other less complex stuff.
But to become a developer, the Skills of solving problems its the Alpha and Omega. Basically it is this what makes the difference between humans and animals, the logic thinking. And the programming language or environment wont be any impediment.
|
|
|
|
|
|
I've met some developers who have almost none of these skills!
|
|
|
|
|
So you have met some managers.
___ ___ ___
|__ |_| |\ | | |_| \ /
__| | | | \| |__| | | /
|
|
|
|
|
Looking for a way to upvote this somehow
|
|
|
|
|
Which I think is a slightly different tinge than problem solving. "Problem solving" is how best to implement a solution once you understand it; analysis is understanding the problem.
For example, our DBA recently discovered that a (really simple) query which hits the database on pretty much every page is running a lot when the database is slower.
Thus, it must be causing the database slowness. Sigh.
In other news, hydrogen is the most abundant element in the universe.
|
|
|
|
|
- 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.
|
|
|
|
|