> So we both embark on a completely needless adventure of changing random parts of the code and scratching our heads as to why nothing makes the error go away. I end up wasting hours because of a typo.
Wow. That's just straight up admitting being an idiot and blaming others for it. If a person leaving out a stack trace causes you to ask for a stack trace that is on them. They wasted some of your time. (Or at least I guess you can argue that.) If a person leaving out a stack trace causes you to blindly modify random parts of the code then that is on you and you only.
Confused people ask confused questions. Because they are confused. If they could ask the right questions they would have already helped themselves. It is your job to not let their confusion overtake you. Ask questions until you understand the situation. Software engineering is not a SWAT raid. You can and should ask questions and shoot only later.
Wow. That's just straight up admitting being an idiot and blaming others for it. If a person leaving out a stack trace causes you to ask for a stack trace that is on them. They wasted some of your time. (Or at least I guess you can argue that.) If a person leaving out a stack trace causes you to blindly modify random parts of the code then that is on you and you only.
Confused people ask confused questions. Because they are confused. If they could ask the right questions they would have already helped themselves. It is your job to not let their confusion overtake you. Ask questions until you understand the situation. Software engineering is not a SWAT raid. You can and should ask questions and shoot only later.