Post History

The real problem was that the question didn't provide it's own context well enough.  Tags aren't content.  They are only for filtering questions to what you want to view, in a search, etc.  It is a misuse of tags to rely on them to provide important context to the question.

Putting tags at the top of a question will lead to even more misuse of tags than we already have.

The better way to address the problem you encountered is to enforce or encourage better questions.  There needs to be more responsibility on question writers to make their questions more accessible.

Questions aren't there only to get answers.  They are also for providing interesting content in general.  Given that most questions only get a few answers and that there are way more users than that, most question readers aren't those who can answer them.  Questions should be written with this perspective in mind.

If you think questions are only for soliciting answers, then consider SE's Hot Network Questions.  People obviously read those for interest, not because they are likely to answer them.

Of course, any specific topic has its jargon.  As examples, we can't expect an electronics question to define a PCB (printed circuit board), a photography question explaining f-stops before referencing them, a cooking question defining what a wok is, etc.  However, if something is more niche, then it should be defined or other context provided.

In the case you cited, the question should have mentioned it was using C++ and the QT library right up front.  If this sort of thing happens too often, it is an indication that the overall site topic is too broad.  I think that's exactly the case for the Software Development site.