Trust me, I’ve tried it. I even starting swearing at the AI Agent recently ![]()
I am not going to claim the AI Agent is human or reached that moment we all dread where it has actual emotions.
However,… something definitely happens.
Not being a behavioural psychologist, I don’t have the fancy words to describe it. However, I think it is probably to do with when we hammer the keyboard with poor instructions, swear at Agent, or bark 3 word instructions. In these situations, we are not actually giving it constructive and details explanations of the issues, requirements, suggestions, etc.
But Agent recognises the harsh words as frustration and urgency to “just get on and do something/anything ASAP”. And so it tries to please us and make the fixes/changes without any real understanding of what we actually want or the bugs we are seeing and need fixing.
This then spirals downwards very fast, as the results continue to fail to live up to what we need.
So, in many ways, when we think Agent is being rubbish, we need to look at what we are saying to it and asking it.
If you said “Your change is f(&(ng cr@p. fix it now you id10t*” to a human developer, do you think they would know what to do? Or do you think they would hurriedly make a quick change just to try and please you, and in fear for their job?
I have observed myself going down these rabbit holes when I am tired and have been vibe coding non-stop for too many hours without a break. It is a definite pattern.
And interestingly, it is an issue many people blame on “the Agent running out of its context memory/window”. When in actual fact, it is us who are tiring and starting to bark rubbish prompts at the agent.
This results in us ending up with the old developer’s adage: Garbage In, Garbage Out
So, the ultimate fix?
If the AI Agent starts making mistakes, it may not be the Agent’s fault or a context issue. It may be YOU who needs to step away from the computer and take a break.