I think it really depends on where in your career you are? Like if you are near the beginning:
* read the whole intro, make sure to look up any parts of the problem description you don’t understand
* at least skim the body of the work. If you are trying to implement a code, make sure to understand all the algorithm blocks and note how each one corresponds to the overall work so you don’t end up implementing a special case.
* read pay extra attention to the conclusion and skim the results
If you are experienced, I guess you don’t need advice, but I figure it is something like:
* skim the first couple sentences (for the problem) and the conclusion of the intro
* skip to the results section to see if the person is screwing you around with gamed metrics
* read the whole intro, make sure to look up any parts of the problem description you don’t understand
* at least skim the body of the work. If you are trying to implement a code, make sure to understand all the algorithm blocks and note how each one corresponds to the overall work so you don’t end up implementing a special case.
* read pay extra attention to the conclusion and skim the results
If you are experienced, I guess you don’t need advice, but I figure it is something like:
* skim the first couple sentences (for the problem) and the conclusion of the intro
* skip to the results section to see if the person is screwing you around with gamed metrics
* go back if it looks good and skim their ideas