Improving the list of perfume query ideas

[bestchai]

Re: QueryIdeas

(1) Start each item from the perspective of a developer -- what
question is a developer asking about their system? For example, "Why
is my system slow when it processes a data packet?" or "Which function
is allocating a large amount of memory?". It would be nice if it's a
simple + short sentence that anyone can understand. But, it's also
okay to give some necessary background information if something cannot
be made clear in a single sentence.

(2) Next, link the question to the Perfume model. How does the
question get translated into the context of the performance model? For
example, "To answer the question with a perfume model, one would need
to find an edge in the model that has the highest weight.". There
might be multiple ways of mapping a question, list as many as you can
think of.

(3) Finally, give the technical/design+implementation solution that
implements an answer to the question. Here you can talk about the
algorithm you would use, particular model constraints, or
server-client communication issues, etc. For example, "Finding the
largest weight is a simple enumeration and sort of all of the edges in
the model. Further, the highest-weight edge can be cached for
performance. The found edge can be highlighted in purple and it can
also have an elegant flashing effect (see JQuery doc X) so that it is
easily noticed."

Finally, it would help if the list of ideas is sorted by
novelty+feasibility. The best ideas (in your opinion) that are
feasible should appear at the top. The ideas that have poor motivation
(i.e., poor (1) above) or are very complex (i.e., in (3) above) should
be at the bottom of the list.

[Issue created by bestchai: 2014-01-28]
[Last updated on bitbucket: 2016-01-20]