One of the challenges of my job is that customers often do not provide enough data regarding their problems. What they do is describe their problem, and assume that their problem can be solved based on that description. I've witnessed this phenomenon both at my previous company and my current company.
Most of these customers probably never encountered or heard of Eric Raymond's "How to ask questions the smart way".
Most of the time, additional data is required. Often, direct ways of asking customers to provide the data doesn't work. In many cases, I had to ask "Would you please provide additional data/steps, such as, xxxxx" 2-3 times before they responded with the requested data. One of the modules in counselling is psychology and a chapter in psychology deals with behaviour. I believe that I can use operant conditioning to influence customers to provide additional data when they file their case.
Let's see how it goes...
Some time ago, I mentioned that I took up a counselling course . Tonight, we begin the study of ethics
In 2017, with the release of Delphi 10.2 Tokyo, Embarcadero introduced a specialized implementation of the Observer pattern into the System.Classes unit. While it has been in the wild for 9 years, it remains a "hidden" architecture for many, primarily because it serves as the invisible engine behind LiveBindings. Other than live bindings, you can also use the Observer pattern as a way to update component settings to the Windows registry, an .ini file, or persist it elsewhere.
System.Classes