Kelson<p>When new people try to use it and have questions, try to answer the question they're actually asking.</p><p>"How do I do X with Y?"</p><p>Instead of answering: "You shouldn't do X with Y! Why would you use Y if you wanted to do X?" Maybe answer like this:</p><p>"Here's how you can do X with Y."</p><p>Or if that's not the best answer, try something like one of these:</p><p>"Y makes it hard to do X, because it's prioritizing W. You can do it this way if you want to, but you might consider Z, which is similar and makes X a priority."</p><p>"Y leaves X off by default because of W, but you can turn it on by doing Z."</p><p>"Y doesn't do X at all because of W, but Z might be a workable alternative for the use case you describe." (W can be anything from a critical design goal to an arbitrary decision to just no one has gotten around to building the feature yet, and Z can be an alternative to either X or Y)</p><p>And most importantly, remember: Their use case for X (or Y, for that matter) is not necessarily the same as yours!</p><p><a href="https://notes.kvibber.com/tags/techsupport" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>TechSupport</span></a> <a href="https://notes.kvibber.com/tags/behelpful" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>BeHelpful</span></a> <a href="https://notes.kvibber.com/tags/tips" class="mention hashtag" rel="nofollow noopener noreferrer" target="_blank">#<span>tips</span></a></p>