![How to contribute to the Flutter engine [Windows]](https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.amazonaws.com%2Fuploads%2Farticles%2F6l3gn3x9ffod81mk92vm.png)
How to handle teammates pressuring me (even publicly) to redo my work after I already explained my reasoning?
I’m a senior software developer and I have been working for a new company for a couple of months. Lately I had this issue where I refactored an old component because the requirements were to reuse for a new task. The original component had multiple issues and was not built with reusability in mind. I reused what was technically feasible and built clean, decoupled modules to support the updated use case. After submitting my pull request, a teammate began repeatedly messaging me - including in a group chat with the architect - pushing me to change my implementation to reuse the older component. I explained my reasoning clearly. I’m open to feedback and take criticism when it’s fair, but in this case the request would have added complexity and technical debt for the sake of reusing a component that wasn’t designed for this context. Despite my explanation, the teammate continued to continuously message things like: “Why don’t you use the component, it’s already built?” “There’s no need to build something new - we can just reuse what’s already there.” In the group chat, in front of the architect, he said: “I think Zaara can just adapt the existing component instead of rewriting it.” Then added that I had introduced "duplication" - which framed my implementation negatively. The architect seems to have picked up the impression that the older component was built with reusability in mind (which it wasn't), and I suspect my teammate may be trying to avoid doing additional refactoring himself. To me, it feels like I’m being pressured to rewrite my code to make the old component appear usable - when in reality, further integration would require more work than it's worth. I also don’t think a full refactor of the shared component is urgent - the current implementation works and is maintainable for the near future. Separately, another teammate recently pressured me by messaging me on and on to approve his PR after I requested changes, saying: “If you don’t like it, you could do changes after my PR is merged.” “No point in delaying it because of that.” I can be flexible - but in these two cases, the pushback was about avoiding poor-quality outcomes, not stubbornness. The team lead is also new and still onboarding, so I haven’t raised this yet. I don’t want to appear difficult or as if I’m resisting feedback - I just want to maintain quality without being overloaded with work someone else doesn’t want to finish. I gathered that despite their use of technical jargon my teammates are not as technically savvy as they want to appear to be, and they try to dismiss my feedback. My new lead told me separately that he'll ask me to be one of few required approvers of their PRs but I don't see how that will work if my teammates continue with this pattern of pressuring me. I find the situation stressful and unproductive, especially when the pressure is applied in front of leadership. I don't want to appear argumentative and difficult to work with especially when I am relatively new to the team. TL:DR; How can I professionally handle a situation where teammates continue messaging and pressuring me - including publicly in front of leadership - after I’ve already provided a clear, valid technical explanation, especially when it seems like the goal is avoiding their own rework?
I’m a senior software developer and I have been working for a new company for a couple of months.
Lately I had this issue where I refactored an old component because the requirements were to reuse for a new task. The original component had multiple issues and was not built with reusability in mind. I reused what was technically feasible and built clean, decoupled modules to support the updated use case.
After submitting my pull request, a teammate began repeatedly messaging me - including in a group chat with the architect - pushing me to change my implementation to reuse the older component.
I explained my reasoning clearly. I’m open to feedback and take criticism when it’s fair, but in this case the request would have added complexity and technical debt for the sake of reusing a component that wasn’t designed for this context.
Despite my explanation, the teammate continued to continuously message things like:
“Why don’t you use the component, it’s already built?” “There’s no need to build something new - we can just reuse what’s already there.”
In the group chat, in front of the architect, he said:
“I think Zaara can just adapt the existing component instead of rewriting it.”
Then added that I had introduced "duplication" - which framed my implementation negatively. The architect seems to have picked up the impression that the older component was built with reusability in mind (which it wasn't), and I suspect my teammate may be trying to avoid doing additional refactoring himself.
To me, it feels like I’m being pressured to rewrite my code to make the old component appear usable - when in reality, further integration would require more work than it's worth. I also don’t think a full refactor of the shared component is urgent - the current implementation works and is maintainable for the near future.
Separately, another teammate recently pressured me by messaging me on and on to approve his PR after I requested changes, saying:
“If you don’t like it, you could do changes after my PR is merged.”
“No point in delaying it because of that.”
I can be flexible - but in these two cases, the pushback was about avoiding poor-quality outcomes, not stubbornness.
The team lead is also new and still onboarding, so I haven’t raised this yet. I don’t want to appear difficult or as if I’m resisting feedback - I just want to maintain quality without being overloaded with work someone else doesn’t want to finish.
I gathered that despite their use of technical jargon my teammates are not as technically savvy as they want to appear to be, and they try to dismiss my feedback. My new lead told me separately that he'll ask me to be one of few required approvers of their PRs but I don't see how that will work if my teammates continue with this pattern of pressuring me.
I find the situation stressful and unproductive, especially when the pressure is applied in front of leadership. I don't want to appear argumentative and difficult to work with especially when I am relatively new to the team.
TL:DR; How can I professionally handle a situation where teammates continue messaging and pressuring me - including publicly in front of leadership - after I’ve already provided a clear, valid technical explanation, especially when it seems like the goal is avoiding their own rework?
