|
I know.
Luckily I am just new, not dumb
M.D.V.
If something has a solution... Why do we have to worry about?. If it has no solution... For what reason do we have to worry about?
Help me to understand what I'm saying, and I'll explain it better to you
Rating helpful answers is nice, but saying thanks can be even nicer.
modified 30-Mar-15 17:38pm.
|
|
|
|
|
Well, often the quality is related to invested time. I usually take more time to do better software than others but there are peoples that write a lot faster than me. Very few peoples are both fast and good.
Philippe Mori
|
|
|
|
|
I disagree, to an extent.
It may seem to take longer, but I find that it saves considerable amounts of time in the long run. The quick, clever code that too no time to write is generally a PITA to modify even slightly when the specification changes slightly, or a bug is found.
As a result, I "do the job properly" even when I am putting together a throwaway app to do one specific task, just once!
Bad command or file name. Bad, bad command! Sit! Stay! Staaaay...
|
|
|
|
|
OriginalGriff wrote: do one specific task, just once
... and no task is ever done just once. If they want it once, they'll want it a million times. With a proper cover sheet.
|
|
|
|
|
Please, find me the Suits who see the sense in this and I'll be on my knees, begging them for a job...
I resigned today because apparently my time management skills are on a junior level... even though I work all hours to get projects done on time (I know I'm slow, see, and I told them), and still manage to write some decent code.
Kills me to ignore all the bad code I'm working on, though.
|
|
|
|
|
In Scrum every member of the Development Team is a Developer (of something: code, tests, excuses, etc.).
Having said that... if the question is limited to "writing code", then I'm the only developer on the team, and even then most of my responsibility is concerned with wrestling with SSIS ( ) . Fortunately, there are enough things that have to be done with code to make the job bearable.
|
|
|
|
|
PIEBALDconsult wrote: excuses
|
|
|
|
|
but I sure make a great guacamole.
|
|
|
|
|
So what 'best' is?
Fastest? Cleanest (bug-free)? Readable? Creative?
If you think you are the 'best' (or the 'worst') you do not understand what team work means...
For instance I'm a team leader of web development. Obviously I know a lot more about design/architecture/tools and so than the one does the actual page development, but it doesn't make me better - or him worst - than others...
In a team everyone have his own part and he supposed to do it according to his! best abilities...But even your part is larger than the others's it doesn't make you best...
Skipper: We'll fix it.
Alex: Fix it? How you gonna fix this?
Skipper: Grit, spit and a whole lotta duct tape.
|
|
|
|
|
You really are a team leader? you're a stuck-up, you're not the best nor the worst .... your choice does not appear in Poll. jejeje
|
|
|
|
|
The Hamsters wrote: Best = the one who writes the most performant, best designed, least buggy code the quickest.
I was completely honest here: "I *am* the team" was an easy one!
But in most teams, everyone knows who is the The Best. Them, every time...
Bad command or file name. Bad, bad command! Sit! Stay! Staaaay...
|
|
|
|
|
For sure - you always get away with it easily...
OriginalGriff wrote: everyone knows who is the The Best. Them, every time That's what brings a team down...
Skipper: We'll fix it.
Alex: Fix it? How you gonna fix this?
Skipper: Grit, spit and a whole lotta duct tape.
|
|
|
|
|
If it's not managed properly, yes.
I've known some seriously useless coders who thought they were The Best (heck I thought I was when I was young) - just look at some of the superstars we get asking questions in QA and publishing "Articles" here! Then look at the usernames, and it's clear they think they are perfect already...
Bad command or file name. Bad, bad command! Sit! Stay! Staaaay...
|
|
|
|
|
Agreed!!!!
I do not fear of failure. I fear of giving up out of frustration.
|
|
|
|
|
The one with no questions.
|
|
|
|
|
There's only one other dev on the team, and he is the better developer of the two of us.
|
|
|
|
|
Happens Half the time
I do not fear of failure. I fear of giving up out of frustration.
|
|
|
|
|
about 25% think the are the top 10% rank. Quit amazing, that a quarter think so visionary.
Mathematic tells another story and also Psychology. "Self bias" is leading to overestimate the own power.
And than yelling about the managers....
Press F1 for help or google it.
Greetings from Germany
|
|
|
|
|
KarstenK wrote: about 25% think the are the top 10% rank. Quit amazing, that a quarter think so
visionary.
One explanation could be that under-average developers don't even bother with CodeProject and other programming communities.
|
|
|
|
|
My thoughts exactly
You'll find a lot of bad programmers on sites like CP and SO, but it's difficult to find good programmers that aren't on CP or SO!
|
|
|
|
|
Sander Rossel wrote: You'll find a lot of bad programmers on sites like CP and SO, but it's difficult to find good programmers that aren't on CP or SO!
in other words... What was first? the chicken or the egg?
M.D.V.
If something has a solution... Why do we have to worry about?. If it has no solution... For what reason do we have to worry about?
Help me to understand what I'm saying, and I'll explain it better to you
Rating helpful answers is nice, but saying thanks can be even nicer.
|
|
|
|
|
|
Yeah! Those of you who think you know everything are very annoying to those of that do!
- I would love to change the world, but they won’t give me the source code.
|
|
|
|
|
To be fair, I voted I'm the best in my team mostly to skew the results.
TBH I don't even assume I'm the best in the room - even when I'm alone
|
|
|
|
|
It really doesn't matter who's the best.
Who's measuring it anyway? How do you measure it in a meaningful way?
I've worked with good devs that were just awful team members. Some others where seen as not so good just because they misplaced in the team (not in their correct role).
It really depends and is too subjective.
Currently my main project includes different technologies so we have a lot of good people from different fields. So at the end, and by this question logic, we have a lot of best-in-the-team members
The most important and also difficult thing is actually to make all of them (more than 30) work as a real team. Some members try to stand out the crowd in a not so unified way and that causes problems.
The management still has to find a proper way to avoid finger-pointing and get-all-the-credit issues but most of the time is their fault anyway.
|
|
|
|