[pawelduda]

Complaining about all these is legit, I'd rather do it and get fired for "underperforming" than push through this shit and burn out. These sound like excuses but could be real issues that should be investigated because maybe it's rotten infrastructure that nobody cared about because it's "unproductive". Other devs can be affected too, apart from the person raising it because they lowered their expectations over time and can handle the suffering for the time being, while waiting second hour for CI to pass

[The_Colonel]

All of these are legit, and that's why they're great excuses. CI works most of the time, but sometimes has hiccups for whatever reason. Everybody gets hit by such issues from time to time, this particular dev is just reeeally unlucky and happens to catch those every other day. But nobody keeps the stats. People might get a hunch something is wrong, but what can you do with that?

[pawelduda]

Offer help with troubleshooting, hop on a call (maybe pair programming), ask what have they tried to solve the problem, etc, etc... If you assume someone is slacking because of common roadblocks, you're setting yourself up for trust issues. If you see they are indeed underperforming, you can take regular steps from there. If they straight up lie it'll be obvious at some point. No need to start with stance of distrust IMO