[pizzaparty2]

Two things.

One, there is no excuse for garbage code. Deadlines don't cause people to suddenly forget how to code. Perhaps corners get cut and things need to be refactored but if developers are coming and going and saying the code is bad I doubt that's just because of a deadline. That sounds more like a bad developer using a deadline as his excuse.

Two, do you have code reviews? Are you looking at their code? Are they looking at yours? Why would you expect them to write triple A code when they have to use what you say is a garbage code base? Garbage code breeds garbage code. 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?

[brianaluv]

>> 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?

[ajeet_dhaliwal]

This isn’t true if you’ve been in a situation where execs are pushing hard to meet a deadline. Corners need to be cut or dates need pushing back, you can’t do both in most cases.