Initial commit: obsidian to gitea
This commit is contained in:
36
study/How to review.md
Normal file
36
study/How to review.md
Normal file
@@ -0,0 +1,36 @@
|
||||
# workflow
|
||||
|
||||
1. read the paper
|
||||
2. look for good ideas
|
||||
3. look for flaws and categorize them
|
||||
4. take some notes while reading
|
||||
5. after 1 day to write review, generating insights and comments in the background and avoiding emotional
|
||||
|
||||
# structure
|
||||
|
||||
1. Summary
|
||||
2. Recommendation
|
||||
3. Strong points
|
||||
4. Major weak points
|
||||
5. Minor points
|
||||
|
||||
# A set of criteria
|
||||
|
||||
- originality
|
||||
- insightfulness
|
||||
- validation
|
||||
- thoroughness
|
||||
- importance of topic
|
||||
- presentation
|
||||
- clarity
|
||||
|
||||
---
|
||||
# What I learned?
|
||||
|
||||
Some papers ...
|
||||
are hard to follow, especially for reviewers who have no background in this topic.
|
||||
are not focus on their main contribution, which can easily make reviewers feel loss.
|
||||
lose a clear presentation about their insights to their methods, feel confused to follow the research path.
|
||||
|
||||
|
||||
|
||||
Reference in New Issue
Block a user