1.learn by practice
2.the paper is posted on a blog. not only the final version of the paper is posted, but also the drafts. i.e. day by day, draft, refine it, refine it again.
This paper discusses in detail the objectives of the practice and the rationale for the main features of the practice. Emphasis is given to the problems raised by the need for good paper writing.
Introduction:
The writing philosophies of the very first practice on paper are discussed in this paper.
Objectives:
Learn from the masters
Start writing papers by practice, and refine it.
Decisions:
Why learn from the masters?
Why learn by imitating?
Why learn by practice?
Why posted on the blog, and why the drafts are also posted?
Conclusion:
Future Works:
Write a good paper of your own and make innovations. (You can see the "Future Works" part is the innovative part of this paper from the original paper " Architecture of the IBM System/360", by imitating which the author learn to write this paper.) You see how the author learn to write from the very beginning to the last.
Appendices:
Acknowledgments:
The workshop lecture given by Kai Li -- "How to write a better paper: Avoid rejections from top systems conferences", the author got the resources from the lecture.
The author acknowledge the readers who are interested in this paper.
The background music the author listening to: Concerto in D Major for Cello and Orchestra played by Yo-Yo Ma.
References:
1.G. M. Amdahl, G. A. Blaauw, F. P. Brooks,Jr. , " Architecture of the IBM System/360 ".
2.Roy Levin and David D. Redell, "An Evaluation of the Ninth SOSP Submissions or How (and How Not) to Write a Good Systems Paper".
3.William Strunk, "The Elements of Style".
4.David A. Patterson, "How to Have a Bad Career in Research/Academia".
2.the paper is posted on a blog. not only the final version of the paper is posted, but also the drafts. i.e. day by day, draft, refine it, refine it again.
This paper discusses in detail the objectives of the practice and the rationale for the main features of the practice. Emphasis is given to the problems raised by the need for good paper writing.
Introduction:
The writing philosophies of the very first practice on paper are discussed in this paper.
Objectives:
Learn from the masters
Start writing papers by practice, and refine it.
Decisions:
Why learn from the masters?
Why learn by imitating?
Why learn by practice?
Why posted on the blog, and why the drafts are also posted?
Conclusion:
Future Works:
Write a good paper of your own and make innovations. (You can see the "Future Works" part is the innovative part of this paper from the original paper " Architecture of the IBM System/360", by imitating which the author learn to write this paper.) You see how the author learn to write from the very beginning to the last.
Appendices:
Acknowledgments:
The workshop lecture given by Kai Li -- "How to write a better paper: Avoid rejections from top systems conferences", the author got the resources from the lecture.
The author acknowledge the readers who are interested in this paper.
The background music the author listening to: Concerto in D Major for Cello and Orchestra played by Yo-Yo Ma.
References:
1.G. M. Amdahl, G. A. Blaauw, F. P. Brooks,Jr. , " Architecture of the IBM System/360 ".
2.Roy Levin and David D. Redell, "An Evaluation of the Ninth SOSP Submissions or How (and How Not) to Write a Good Systems Paper".
3.William Strunk, "The Elements of Style".
4.David A. Patterson, "How to Have a Bad Career in Research/Academia".
没有评论:
发表评论