|
But ... That is what "Experience" is - the ability to recognize an error when you repeat it!
|
|
|
|
|
trønderen wrote: That is what "Experience" is - the ability to recognize an error when before you repeat it!
"I have no idea what I did, but I'm taking full credit for it." - ThisOldTony
"Common sense is so rare these days, it should be classified as a super power" - Random T-shirt
AntiTwitter: @DalekDave is now a follower!
|
|
|
|
|
If you are not making the occasional mistake, something is off.
Our technologies are constantly evolving, and we should be trying to use some amount of (proven) techniques if it makes sense. But that means mistakes are possible as we learn.
Linters, code reviews and other such techniques can help with catching these.
|
|
|
|
|
Sometimes, a bug is just that, a bug.
People hit an edge case that's not handled correctly, or one in ten values is slightly off, whatever.
Sometimes, the mistake is that a (part of a) program won't run at all and it's obvious the programmer hasn't even tested (manually or otherwise) their code.
I'm a lot more forgiving to the former than to the latter.
The latter is just lazy and bad programming.
|
|
|
|
|
I work with one of those. Doesn't even compile the code before checking it in, much less tests it. And merges stuff unbidden.
I’ve given up trying to be calm. However, I am open to feeling slightly less agitated.
|
|
|
|
|
logically thinking through the code if will work and thinking of breaking things.
like being told, "you need null check on this"
me: uhm no, because to get to this section, it needs to pass a bunch of other stuff which would fail way before if null check here was an concern
vs - runs once, must be ok.
|
|
|
|
|
If they're aggressively ignorant and unwilling to learn good development techniques. That's unforgiveable.
People that make obvious mistakes due to lack of experience, but are willing to learn and grow from it, are going to be better developers. That's OK.
|
|
|
|
|
I mean, it's easy to point with the finger at that one colleague, that screwed up the function or committed that awful bug.
As I am most of the time in a leading role in the projects I do or have at least due to my seniority a bit of responsibility assigned, I always take the time to reflect and I try to see the whole picture. "Could I have done anything to avoid that?", "How could it pass the code reviews?", "Did I fail in teaching properly?"
No matter if you're in the job or in a match of Rocket League or in a raid in WoW or even out there in your car in a critical traffic situation... Finger pointing is easy, questioning yourself about YOUR role in that situation, is a hurting task and needs discipline and analysis.
Back to code mistakes... The survey asks "how forgiving WE are" -- well, this implies, that we are CLOSE ENOUGH to the situation to recognize it, so we are close enough to the product/project whatever. And therefore, we should also reflect our own role.
How forgiving are you to YOUR OWN mistakes? And do you even see them?
modified 31-Oct-22 2:05am.
|
|
|
|
General 
News 
Suggestion 
Question 
Bug 
Answer 
Joke 
Praise 
Rant 
Admin 
Submit an article or tip
