I've reviewed many, many research papers over the years, and it occured to me that the task is largely automatable. At least it feels like I keep writing the same reviews over and over again... Perhaps the problem is that people just don't know how to write a good computer architecture research paper. With that in mind, I've created this handy flow chart to help you write a better paper (and recognize a good paper when you read one). And maybe, just maybe, it will mean that I get to review more good papers =). Comments are welcome.
