Simply put passive/aggressive is saying one thing and doing another – it’s obviously more nuanced than that, but this is basically what it comes down to.
In a work context it can look like someone saying they are on board with something but then acting in a way that shows they’re clearly not; picture a meeting where the boss asks you if you’re on board, you nod in agreement and then their back is turned you pull a face that shows others you clearly didn’t mean what you just said.
If that person is a direct report, then you will recognise it as passive/aggressive if they never seem to follow through on their commitments.
One way to manage the situation is to get them to say what they are going to commit to doing rather than you telling them what you want them to commit to and then hold them to account to do it. It’s a subtle difference but if they are the ones volunteering the commitment, you less likely to get BS from them. If they still don’t follow through, then you can directly ask them why not, pointing out that it was they that made the commitment.
It won’t neccessarily cure the problem, but it makes managing them (out) easier.
sounds like every programmer I’ve ever worked with.