Return to Answer

"I'm an accomplished software architect and it was a breeze. The new code is fully unit testable with dependency injection and comprehensive logging, so any bugs and problems are super easy to track down, reducing the number of man-hours required for bug-fixing and maintenance work, and therefore reducing costs involved in these labours"

"I'm an accomplished software architect and it was a breeze. The new code is fully unit testable with dependency injection and comprehensive logging, so any bugs and problems are super easy to track down, drastically reducing the number of man-hours required for bug-fixing and maintenance work, and therefore reducing costs involved in these labours, by both making it much easier for developers to find the problematic code and by detecting problems with new code in newer versions before they reach the next stage in the development lifecycle."

#3. Throw in some management lingo

#3. Throw in some management point-of-view

#1.

#2.

#3.

#4.

Now, let's address your teammate's argument for keeping the original code: 'It works'. Okay, maybe it doesn't always work, but it's been relied on for some years now. You can propose to management to have a test system running with your implementation concurrently with another system running the original code. This way, your teammate no longer has that argument because you've proven to everyone that your code also works.

#5.

#1. Don't belittle others or come from a place of arrogance

#2. Ease up on the technical lingo

#3. Throw in some management lingo

#4. Address your teammate's concerns

Now, let's address your teammate's argument for keeping the original code: 'It works'. Okay, maybe it doesn't always work, but it's been relied on for some years now. You can propose to management to have a test system running with your implementation concurrently with another system running the original code. Maybe even fire off a few test-cases, including some that you expect to break the original code. This way, your teammate no longer has that argument because you've proven to everyone that your code also works, and even works better.

#5. Address unmentioned (but still important) factors

Only when you have addressed these 5 points can you get around the following problem:

The issue is that management look at both of us and don't know who to believe.