> Seems like they're not using the tool correctly To their defense they openly admit this > and didn't read the documentation. They clearly did, they even li

> Seems like they're not using the tool correctly To their defense they openly admit this > and didn't read the documentation. They clearly did, they even linked to it. But, as a sibling comment mentioned, they could probably got away with a basic get instead. As documentation writers (and often that should be read "as developers") it is our task to make our users fall into the success pit - and stay there. Unfortunately, by not considering this, thousands of hours get lost every year and lots of potential users leave because they were somehow (Google, random blogs, our documentation) led into the hard path. My favourite example is how, for years, if you tried to find out how to use an image in a Java application you would end up with the documentation for an abstract class 2dgraphics or something, while the easy way was to use an Icon.