[acesubido]

This:

"There's a feature you and several other co-workers are building. The deadline is 3 days from now.

You and 'Co-worker A' are tasked in building a module of that feature. You've already written several classes and tried abstracting some repetitive parts that would allow you to hit the target deadline for the team.

However 'Co-worker A' has also worked on those same classes and wrote more methods that are too tightly coupled and doesn't read well underneath. He claims this is a better design than yours just to finish the feature and doesn't budge on changing it during code reviews.

How do handle this situation?"

I like this question since there's a wide range of answers of how people deal with conflict under pressure.

[mcv]

A deadline 3 days from now and we're still discussing how we're going to approach it? Does it need to be in production? Does it need to be tested and deployed? I think I'd first inform our stakeholders that we've got a delay and are not going to make the deadline unless we drop this feature.

[duiker101]

Cool question, I would probably agree just to get the feature out (if it's really essential) but at the condition that the first thing that will be done after release is to change those methods otherwise it will never be done.

[ashwnacharya2]

This is a very brilliant question. Thank you!

[vegiraghav]

give the finger to Mr.A ?