One thing i can share from my experience is, some people communicate poorly because of laziness.
In this case, Even if the vague communication is understandable to you since you are aware of the dev's current WIP, pretend you don't understand and nudge the developmer to add more details for the context as necessary.
For example let's say your team has 5 services. The developer pings you : when starting the service i am facing this exception, tried different ways couldn't figure out, can you please help? .
Questions : Which service is he trying to start? Which machine is he trying to start?(local/virtual).
He probably doesn't mention these details because he thinks you must be aware of what he is working on. Even if you know the same, you can ask these questions and ask to mention such infos going forward to improve their communication.
The idea is to communicate clearly as with any developer and not to take things for granted due to laziness in typing the relevant details.
In this case, Even if the vague communication is understandable to you since you are aware of the dev's current WIP, pretend you don't understand and nudge the developmer to add more details for the context as necessary.
For example let's say your team has 5 services. The developer pings you : when starting the service i am facing this exception, tried different ways couldn't figure out, can you please help? .
Questions : Which service is he trying to start? Which machine is he trying to start?(local/virtual).
He probably doesn't mention these details because he thinks you must be aware of what he is working on. Even if you know the same, you can ask these questions and ask to mention such infos going forward to improve their communication.
The idea is to communicate clearly as with any developer and not to take things for granted due to laziness in typing the relevant details.