Here the discussion between two programmers is being compared to a car being taken to a workshop (mostly to a person whom u dont interact with on a daily basis)

Here the discussion between two programmers is being compared to a car being taken to a workshop (mostly to a person whom u dont interact with on a daily basis) When a programmer says to another programmer it "does not work", there is usually some history between these programmers where they have some level of understanding between them. This article kinda ignores that aspect. I had never heard someone complain that it "does not work" when there is a compilation error. That is just what a non-programmer or a beginner would say who is trying to get attention for help. This example doesnt fit with the point the article is trying to make. When someone says it "does not work", it is usually followed by a long pause, where the programmer is still wondering why it is not working. The other programmer usually gets that and they patiently wait to hear the details or ask questions because they had been there themselves. It all boils down to what level the two programmers had worked together before and having an idea of when someone would use such a phrase without giving any explanation. Usually the other programmer already has a context of what might not be working). If your scenario does not fit with my explanations, all I can say is that, the other people is stuck and needs some input or someone to challenge his thinking to debug it better. If someone says that, all you have to do is reply back saying "what do you mean?" and you will get flooded with information.