Reach out to that person in private. Talk to them, find out why they implemented that code this way.
There is a reason why SO is so beneficial to the Developers. Many people ask questions(newbie, stupid, or smart) on that platform and the good peer reviewed comments from the experts is documented right there. That encourages people to learn in public and share their knowledge.
Similarly, I prefer the discussions to happen in a common place such as a GitHub PR or on the related GH/Jira issue. Team should be encouraged to take a look at them and have an understanding of the reasons behind a specific implementation.
The problem might be the mindset of the team members who think that asking too many questions about an implementation means it's bad code or the implementer isn't skilled enough.
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.
There is a reason why SO is so beneficial to the Developers. Many people ask questions(newbie, stupid, or smart) on that platform and the good peer reviewed comments from the experts is documented right there. That encourages people to learn in public and share their knowledge.
Similarly, I prefer the discussions to happen in a common place such as a GitHub PR or on the related GH/Jira issue. Team should be encouraged to take a look at them and have an understanding of the reasons behind a specific implementation.
The problem might be the mindset of the team members who think that asking too many questions about an implementation means it's bad code or the implementer isn't skilled enough.