brianaluv

>> To the author, I've experienced this from both sides,

So do I. And it's true that it can sometimes be difficult to admit that I didn't write very good code. But I always think that what needs to be done must be done. That is why I agree to change my code or don't mind having it changed by someone else when I am shown that it is not correct or that it can be improved. In fact, my question has little to do with technology. It's just human relations advice in a workspace I'm looking for, and you seem to have understood it better than others.

I'm not defending poor quality code. I'm looking for a way to avoid someone being insulted because they've written bad code. That's all. Do you ridicule or insult your current colleagues because they have written bad code? If you don't, why would you do it for the people who were on the project before you?

>> One, there is no excuse for garbage code. Deadlines don't cause people to suddenly forget how to code.

Come on, really? I just gave one or two examples to illustrate my point! And they are valid examples (you even partially admitted that in your comment). Also, if you read the discussion, another user gave other reasons that can explain a bad code base.

>> Maybe their arrogance is a way of venting their frustration with being forced to write bad code? Or maybe they're telling the truth but for some reason you interprit it as arrogance? Should I even comment on this? really?

Also, did I even say or imply that the whole codebase is garbage or something?

I understand what you mean. However, I said earlier that I have no problem with improving poorly written code. But I also said that I spent enough time on this particular project to know that some problems that existed before (and no longer exist today), prevented us from writing clean code and were not related to the quality of the developers (some of whom are making fun of today). In other words, the problem is not that the old developers didn't know how to produce good quality code, it's that they didn't always have the possibility. Come on, do you all work on projects where everything runs as smooth as you want?

>> It takes experience and maturity to find productive ways of channeling that feeling. People don’t always get there right away. If you think you have, model it. Show healthy ways of dealing with the “holy shit this is garbage” feeling. If I knew, I wouldn't have asked the question.

But your answer makes me think that the term "arrogance" I used in the title of my question may be too strong...I dunno...

Well, would it make any difference if it was my code? It doesn't matter to me. I certainly produced some low quality code here and there. So what? I don't mind correcting it or having it corrected. But I am a human being and as such, I try to treat those with whom I work (or have worked) as I would like to be treated. Which excludes making fun of them or ridiculing them.

As for my salary, I'm not complaining about it either. Also, I'm not a dinosaur like you seem to think.

>>And author of this question will stay... bound by his insecurity of his unprofessionalism.

Could you elaborate?

That's exactly what it is. Does the fact that I have succeeded in doing a task better than another person (knowing above all that the context is not the same) give me the right to ridicule or criticize him/her beyond necessary? That's why I think the strategy suggested by m0zg may have limits... But again, this is the first time I'm confronted with this situation, so I don't really know.