Why coding skills are not enough for a developer to get hired
-
-
Good article. Having good technical skills, whilst important, is not everything. I've worked with some really good developers who were real jerks. They wouldn't budge in their opinion as they thought they were always right. They wouldn't take positive criticism on board. In short, they didn't listen to those around them.
"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
-
Nice article.
Pankaj Maurya Sr. Software Engineer Gurgaon, India
-
Good article. Having good technical skills, whilst important, is not everything. I've worked with some really good developers who were real jerks. They wouldn't budge in their opinion as they thought they were always right. They wouldn't take positive criticism on board. In short, they didn't listen to those around them.
"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
C.A.R.Hoare, wasn't he the author of the billion-dollar mistake? "
Quote:
I call it my billion-dollar mistake. It was the invention of the null reference in 1965. At that time, I was designing the first comprehensive type system for references in an object oriented language (ALGOL W). My goal was to ensure that all use of references should be absolutely safe, with checking performed automatically by the compiler. But I couldn't resist the temptation to put in a null reference, simply because it was so easy to implement. This has led to innumerable errors, vulnerabilities, and system crashes, which have probably caused a billion dollars of pain and damage in the last forty years. Tony Hoare, 2009.
"If you don't fail at least 90 percent of the time, you're not aiming high enough." Alan Kay.
-
Good article. Having good technical skills, whilst important, is not everything. I've worked with some really good developers who were real jerks. They wouldn't budge in their opinion as they thought they were always right. They wouldn't take positive criticism on board. In short, they didn't listen to those around them.
"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
In my experience these are not good developers, but developers still doing what they were doing ten years ago because it was the right way then.
-
It is best to know one or two languages in a professionell level. Knowing what is possible, in which time and "get it done" in that way. Coding skills are more like "basics", more often is team discipline needed to meet targets as features and termins. Important is to bring this skills into the project with other peoples. I work normally on "user software" where only one or two "high skilled" algorithms or protocols are involved, but tons of nice UI and error handlings.
Press F1 for help or google it. Greetings from Germany
-
Good article. Having good technical skills, whilst important, is not everything. I've worked with some really good developers who were real jerks. They wouldn't budge in their opinion as they thought they were always right. They wouldn't take positive criticism on board. In short, they didn't listen to those around them.
"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've known an expensive, freelance, 'architect' like that. He belittled me in a very rude manner. Then changed working code (literally 15 lines of code), wrote some unit tests, and made it fail miserably in production (which cost me a few hours to find) :D The code he changed didn't need using statements, he said. The GC would take care of disposing my objects, so I didn't need to do that explicitly :sigh: What really failed was an extra ExecuteNonQuery(), which he put in there for no reason at all... First our manager told him NEVER EVER EVER to change working code again. Then I showed him you really need to dispose your objects (by locking a file and not disposing). And after all that he still thought my code was in dire need of change, disposing was unnecessary and he really didn't do anything wrong... :~ X|
Visit my blog at Sander's bits - Writing the code you need. Or read my articles at my CodeProject profile.
Simplicity is prerequisite for reliability. — Edsger W. Dijkstra
Regards, Sander
-
Just as with a hammer, knowing how is the easy part; knowing when and where and why requires many years of experience.
