reduce the scope and focus on details when it comes to implement tiny simple effective methods with single responsibility (and all other solid principles) and be able to unit test and debug "surgically".
move away from those lines of code and get an eagle eye view, understand the big picture, the context where your piece of code works.
and while zooming in and out, be creative and bold and challenge the status quo, pointing out flaws and suggesting solutions or improvements
too often we put ourselves in a cage and implement crazy complicated solutions only because we did not ask the developer close to us (working on same feature but different subtask) to change the return value of the method they are implementing...
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
the ability of Zooming In and Out, meaning:
and while zooming in and out, be creative and bold and challenge the status quo, pointing out flaws and suggesting solutions or improvements
too often we put ourselves in a cage and implement crazy complicated solutions only because we did not ask the developer close to us (working on same feature but different subtask) to change the return value of the method they are implementing...