---- Startup RantLife ----

A senior developer joined the team, let's name him Bob, and this guy is really good no doubts about that.
He made suggestions, some improvements, but Bob is always waving his hands and says out loud that some part of the code base is really really bad.
I kept quiet until one day I had to pair with Bob to check a feature. Guess what happened, as usual, Bob clenched his fist and start pointing that this code is super ugly.
So let's check the history of changes and boom, Bob was the main writer.
That moment, I was completely silent, trying not to smile as Bob came up with an excuse, he never admits that he is wrong, now he needs a scapegoat and he starts blaming the process, the planning...
I believe that being humble and saying sorry is a quality that it requires time to develop.
So don't be like Bob, please :)

<rant>
How the hell do these people have a senior position?
<rant-cause>
Sdev:"The are no vulnerabilities in my code because i have Avast running at the same time"
</rant-cause>
SecOps: "<insert potoo bird reaction>"
</rant>

---- Startup RantLife ----

In this episode, we introduce Brian, this guy is skilled and tries to provide an answer or explanation for everything (even if it's not work related).
By now you may guess this is the one that I know everything and you should listen to me type.

The problem with Brian that he wants only his solution to things and to be written exactly as he sees it and arguing with him is a waste of time.

How do you guys deal with developers like Brian?