Damn, I was wrong... ;)
I guess I should also clarify (if it wasn't obvious), I am speaking about enterprise software development at large scale, and probably none of this properly applies to single OSS with 4 devs (or similar).
My intent was not "senior devs ok to be arrogant", but more so give my understanding of why a lot of senior devs come off as arrogant (if code is dumb, it is okay to say it is dumb, and is not a personal attack).
Simply saying "this code is dumb" and walking away is arrogant -- agreed.
Commenting in code review "this code is dumb" and nothing else is arrogant -- agreed.
Saying "this code is dumb" and debating the concepts at play in code, is not arrogance, but is often perceived as ad hominem ("well [dev] invested tons of time and energy on writing that code you just called dumb and is offended" -- why is [dev] working in a silo to the point that the code is trashed in code review on pull request?).
It's hard not to conclude that you are exactly the type of person my original post is about.
Correct, I was trying to give a why, directly from someone often perceived as an arrogant asshole senior dev.
You also state that human emotions don't belong in software development
Maybe it is better to say "feelings belong in process, not code". I consider everything I discussed process. Code taking down prod at 3am is not, but more of an indicator of bad process (in whatever form).
it just displays emotions you feel are justified, while those felt by others are not
This is interesting. My comment doesn't reflect my actual feelings on this topic, but rather my current understanding of this phenomenon I (clearly) struggle with, based on my experience in industry.
My actual feelings align more with "I am blunt and don't care about your feelings. This is a business not a personal project, get over it." and acknowledge that is arrogant, shitty, and not helpful (probably the other fancy words you used too) but saves ME hours upon hours weekly, which I then get to work on my code/tickets during, which is what my job actually is, and is the ACTUAL metric by which success is tracked.
If you are looking for design review, ask an architect (not through PR to main, which most often indicates "ready"), that is their job, not developers. If you ask for my review I will give it, and that is the "to be nice part". If I look and want to comment "this code is dumb -- rant", and I am the proper reviewer, I ask my manager to help me navigate the best way to express myself without coming off as an asshole.
I also acknowledge I do not write the checks, and have many times over written "dumb code" when that is what the business wants. Although I do make sure and be clear that it is dumb code (business people dgaf until the downtime happens tho).
I saw you ask somewhere on some instance about something similar to a repost bot and thought you may be interested in rss feed bot