<div dir="ltr">The second part of the great talk from last Monday will be given tomorrow.<br><br><div class="gmail_quote">---------- Forwarded message ----------<br>From: <b class="gmail_sendername">Liran Shapira</b> <span dir="ltr"><<a href="mailto:liransh@cs.technion.ac.il">liransh@cs.technion.ac.il</a>></span><br>
Date: Wed, Nov 13, 2013 at 3:15 PM<br>Subject: CSL Luncheon: Thursday, 14.11.2013, 12:30<br>To: <a href="mailto:CSL-L@listserv.technion.ac.il">CSL-L@listserv.technion.ac.il</a><br><br><br>CSL Luncheon: How To Write A Good (Systems) Paper<br>
<br>
Date:Thursday, *14.11.2013, 12:30*Place:Room 337-8 Taub Bld.<br>
<br>
I remind everyone that between 13:00-13:45 Gernot Heiser---the dude who<br>
headed seL4 (the only formally verified OS kernel)---is giving the<br>
following talk:<br>
<br>
TITLE:<br>
How to write a good (systems) paper<br>
<br>
ABSTRACT:<br>
Much good work fails to get the recognition it deserves because it does not<br>
get published in high-profile conferences. The good venues are highly<br>
competitive, and PC members have to review a large number of papers, and<br>
generally look for deficiencies to eliminate papers. For a paper to be<br>
accepted, it must not only have good ideas, it requires a convincing case<br>
that it addresses a relevant problem, and does a convincing job of solving<br>
the problem. Besides that, it must be presented well, as the reviewers do<br>
not have the time for archaeological exercises. This talk focuses on what I<br>
call "paper engineering", a systematic approach to turning an idea into a<br>
publishable paper. It is primarily focused at the "systems" community, but<br>
much of it should apply to other areas of experimental computer science.<br>
<br>
<br>
<br>
We look forward to seeing you.<br>
</div><br><br clear="all"><div><br></div>-- <br>Orna Agmon Ben-Yehuda.<br><a href="http://ladypine.org">http://ladypine.org</a>
</div>