In a team it is generally good to be able to discuss approaches without becoming angry, shouting and leaving the meeting. Performance does not just encapsulate

In a team it is generally good to be able to discuss approaches without becoming angry, shouting and leaving the meeting. Performance does not just encapsulate the code you produce, especially as a senior engineer. After he left the team, the in-mem implementation was removed being widely recognized as a roadblock to building new features (needing to implement an in-memory version of sql WHERE clause or ORDER BY just to add new features to a web app that was backed by an actual SQL DB was error prone and there are many better solutions to testing your DB code) The PR review was another explosion from people questioning his further development of this crazy complex in-men SQL implementation, and the questions were well founded but he was getting very irate at having to constantly defend this thing he was building that others on the team found to be a time suck. This is definitely one sided, it was one of the most difficult situations for me to traverse as I’d never been in a situation where a coworker was what I would characterize as abusive to me and others on the team, so I still can’t really approach it fully objectively.