|
If you have that, most of the others follow (with the possible exception of the ability to code ).
Freedom is the freedom to say that two plus two make four. If that is granted, all else follows.
-- 6079 Smith W.
|
|
|
|
|
Let me start with an assumption that the Code Project's (“for those who code”) survey is mostly taken by those who code. And it's hard to think that “these who code,” viz. we the software engineers, would be able to do our job if we did not know how to code. Coders code. Am I making sense so far? Apologies if this sounds like ramble and gabble. All I've said so far seems nearly a tautology, but I want to establish a sound premise.
Astonishingly, only slightly over 50% of (presumably) “those who code” regard their fellows' ability to do same as important. The two runners-up are intelligence and ethics; no surprise here. Work ethics is priceless, and intelligence and common sense are tremendously nice to have. But the art of sticking this funny main between that odd int and the weirdly curved ( is paramount to our craft. Possessing St. Paul's ethics and Einstein's intelligence are virtues that, in themselves, still fall short of making someone who cannot code a software engineer.
I am flabbergasted. What does this figure tell us? I hope the statistics is somehow skewed, but I cannot plausibly explain how that could be possible, given this site's (again, presumed) audience.
For reference, I ticked coding, intelligence, and ethics.
|
|
|
|
|
I'm just guessing here, but if you've ever had to work closely with a colleague who steals your lunch each day (but you don't know which one it is); an idiot whose real-world problems are frequent and intrusive; who shouts into handsfree all the time; who cycles 10 miles to work and sits there unshowered for the rest of the day; who is frequently absent because of (or badly hungover from) the night before you'd probably rate "ability to code" a little less important.
I also assume that we measure "ability to code" against our own - personal - rating of our ability. Since we are all stellar, godlike developers, we don't expect everybody else to reach that standard - indeed, many would not want the competition - so we rate ability as less desirable in cow-orkers.
And don't forget, we work with many other "branches" of the company: we work with sales, support, logistics, management, admin, accounting, ... none of which we expect to be able to code worth a damn!
Sent from my Amstrad PC 1640
Never throw anything away, Griff
Bad command or file name. Bad, bad command! Sit! Stay! Staaaay...
AntiTwitter: @DalekDave is now a follower!
|
|
|
|
|
I have been compiling a long list of what not to do when coding in C++ (some time C#). The sad part is that I am no longer surprise when I see code that shows that the developer does not actually understands the language they are programming in.
Have fun with this one
if (!string(pString).empty() && pString != NULL && pString != "")
INTP
"Program testing can be used to show the presence of bugs, but never to show their absence." - Edsger Dijkstra
"I have never been lost, but I will admit to being confused for several weeks. " - Daniel Boone
|
|
|
|
|
What we all want, at heart, is someone who is very nearly as good as we are but unlikely to become any better.
Whenever you find yourself on the side of the majority, it is time to pause and reflect. - Mark Twain
|
|
|
|
|
?
«Where is the Life we have lost in living? Where is the wisdom we have lost in knowledge? Where is the knowledge we have lost in information?» T. S. Elliot
|
|
|
|
|
: )
"If we don't change direction, we'll end up where we're going"
|
|
|
|
|
There is important to know about co-worker ability to accept the common rules of united work processes (not only development but interactions and communications between colleagues). We can change bad or uneffective rules, but at first we must accept them before we start to work together. Elsewhere we can not get the Result.
|
|
|
|
|
There ability to accept responsibility for mistakes ?
|
|
|
|
|
I think that was the snarky point of that "mistake"!
Da Bomb
|
|
|
|
|
"Their" is the plural possessive pronoun, not "there."
«Where is the Life we have lost in living? Where is the wisdom we have lost in knowledge? Where is the knowledge we have lost in information?» T. S. Elliot
|
|
|
|
|
...have to be a grammar freak too.
"Their ability to accept responsibility for mistakes" FTFY
|
|
|
|
|
|
All the above, with Hiding the Bodies in the *required list.
If you think 'goto' is evil, try writing an Assembly program without JMP.
|
|
|
|
|
I look for someone like me. Not by race or gender, but by character, temperament, intelligence, discernment, culture, language, and experience.
I can take (and have taken) a smaller number of software engineers by my standards and produce more and better than a larger team of software engineers by contemporary standards - all within the same budget for each.
You may not like my answer, but at least it is honest and a proven solution.
|
|
|
|
|
With honesty, you get a most of the other important behaviors.
|
|
|
|
|
My company has this huge push on diversity and inclusion. Drives me nuts because the implication is that I am a bigot when I truly don't care how you "identify" yourself. I only care if you are at least as competent as I am.
|
|
|
|
|
But the real answer is someone competent who can work on a problem to do a good job; give and accept advice - an not have an ego about it. A gestalt member.
Ravings en masse^ |
---|
"The difference between genius and stupidity is that genius has its limits." - Albert Einstein | "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 |
|
|
|
|
|
W∴ Balboos wrote: A gestalt member
Aha!!
|
|
|
|
|
In other words, someone who will pitch in and help get the job done. They don't just sit on their small piece of the work, shout "Finished!", and sit on their lazy ass while the rest of the group is humping over a problem.
Software Zen: delete this;
|
|
|
|
|
Gary Wheeler wrote: and sit on their lazy ass while the rest of the group
I was just trying to stay out of the way.
|
|
|
|
|
I haven't had this problem often, but when it does it's really infuriating. The worst case was a hardware engineer working with me on a custom modification for a customer. He refused to help me debug the driver for his hardware, essentially pointing at his logic analyzer saying "there it is; it works". Bastard.
Software Zen: delete this;
|
|
|
|
|
I had this happen when creating an API.
The caller of the API had a bug in his software but thought I should fix it because he was calling my API.
|
|
|
|
|
plus don't eat smelly food at your desk.
Keep your friends close. Keep Kill your enemies closer.
The End
|
|
|
|
|
pass on the "hide bodies"
If they help me, then they will expect me to help them at some point. No thanks.
|
|
|
|