<?xml version="1.0"?>
<feed xmlns="http://www.w3.org/2005/Atom" xml:lang="en">
	<id>https://istlab.dmst.aueb.gr/wiki/api.php?action=feedcontributions&amp;feedformat=atom&amp;user=193.92.228.97</id>
	<title>Istlab - User contributions [en]</title>
	<link rel="self" type="application/atom+xml" href="https://istlab.dmst.aueb.gr/wiki/api.php?action=feedcontributions&amp;feedformat=atom&amp;user=193.92.228.97"/>
	<link rel="alternate" type="text/html" href="https://istlab.dmst.aueb.gr/wiki/index.php?title=Special:Contributions/193.92.228.97"/>
	<updated>2026-11-15T09:46:09Z</updated>
	<subtitle>User contributions</subtitle>
	<generator>MediaWiki 1.43.9</generator>
	<entry>
		<id>https://istlab.dmst.aueb.gr/wiki/index.php?title=SENSE_publication_plans&amp;diff=1933</id>
		<title>SENSE publication plans</title>
		<link rel="alternate" type="text/html" href="https://istlab.dmst.aueb.gr/wiki/index.php?title=SENSE_publication_plans&amp;diff=1933"/>
		<updated>2007-04-17T06:48:11Z</updated>

		<summary type="html">&lt;p&gt;193.92.228.97: Add discussion&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;A good publication record doesn&#039;t happen by chance.  It requires careful planning and execution.    Given the fact that publishing to a top journal can take as much as three years, you can&#039;t afford to send a publication off, and then wait for a reply.  At any time you should have a pipeline filled with publications in three stages of progress.&lt;br /&gt;
&lt;br /&gt;
* Publications under development.  These may be new contributions or papers that you improve following review comments.&lt;br /&gt;
* Publications under review.&lt;br /&gt;
* Publications that have been accepted and are (often slowly) moving toward publication.&lt;br /&gt;
&lt;br /&gt;
Keeping all stages of the pipeline full ensures that publishers, reviewers, and yourself are always busy, with no time being lost in idle waiting.  Also, try to have in your pipeline a mix of different paper types: conference papers for rapid dissemination of results; journal articles for advancing your academic career.  Publication delays being what they are, your first aim in your plan is to keep reviewers and publishers busy.  Don&#039;t sit on papers that have been accepted with revisions: revise them as soon as possible.  If you ever notice that a stage of your pipeline is empty, you&#039;re in trouble.  Make it your priority to fill it up, or prepare to cry over an empty hole in your CV&#039;s publication record.&lt;br /&gt;
&lt;br /&gt;
== Plans of individual members ==&lt;br /&gt;
* [[Publication plan template]]&lt;br /&gt;
* [[Diomidis Spinellis publication plan|Diomidis Spinellis]]&lt;br /&gt;
* [[Giorgos Gousios publication plan|Giorgos Gousios]]&lt;br /&gt;
* [[Vassilios Karakoidas publication plan|Vassilios Karakoidas]]&lt;br /&gt;
* [[Panos Louridas publication plan|Panos Louridas]]&lt;br /&gt;
* [[Stephanos Androutsellis publication plan|Stephanos Androutsellis]]&lt;br /&gt;
* [[Kostas Stroggylos publication plan|Kostas Stroggylos]]&lt;br /&gt;
&lt;br /&gt;
== Discussion ==&lt;br /&gt;
===Isn&#039;t it risky to open-up my publication plan?  Somebody might steal my idea.===&lt;br /&gt;
We are researchers, not the CIA.  The risk isn&#039;t our ideas leaking into the open, but our ideas not getting disseminated.  Also, ideas are cheap, execution is difficult.  So publish your plan, and concentrate on getting your publications quickly to print.&lt;br /&gt;
&lt;br /&gt;
[[Category:SENSE]]&lt;/div&gt;</summary>
		<author><name>193.92.228.97</name></author>
	</entry>
	<entry>
		<id>https://istlab.dmst.aueb.gr/wiki/index.php?title=Diomidis_Spinellis_publication_plan&amp;diff=1932</id>
		<title>Diomidis Spinellis publication plan</title>
		<link rel="alternate" type="text/html" href="https://istlab.dmst.aueb.gr/wiki/index.php?title=Diomidis_Spinellis_publication_plan&amp;diff=1932"/>
		<updated>2007-04-17T06:42:16Z</updated>

		<summary type="html">&lt;p&gt;193.92.228.97: Resubmit SDriver&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;== Under development ==&lt;br /&gt;
* Emulating the Antikythera Mechanism on Squeak EToys.&lt;br /&gt;
* Sourcing Open Source Software. (HBR; 2007-03-30.)&lt;br /&gt;
* Going Functional on Exotic Trades. (With S. Frankau et al.  &#039;&#039;Journal of Functional Programming&#039;&#039;. Q3 2007).&lt;br /&gt;
* Mentoring in Open Source Projects. (With N. Bozionelos; Q4 2007).&lt;br /&gt;
* Development Infrastructures. (&#039;&#039;IEEE Software&#039;&#039;, 2008).&lt;br /&gt;
* SDriver: Location-Specific Signatures Prevent SQL Injection Attacks.  (With D. Mitropoulos; &#039;&#039;Computers and Security&#039;&#039;).&lt;br /&gt;
&lt;br /&gt;
== Pending ==&lt;br /&gt;
* Τhe Antikythera Mechanism: a Computer Science Perspective.  (Computer; 2007-03).&lt;br /&gt;
* Phone tapping in the 21st Century.  (With V. Prevelakis; &#039;&#039;IEEE Spectrum&#039;&#039;).&lt;br /&gt;
&lt;br /&gt;
== To appear ==&lt;br /&gt;
* Another Level of Indirection. ([http://www.amazon.com/Beautiful-Code-Leading-Programmers-Explain/dp/0596510047/sr=8-1/qid=1170619333/ref=pd_bbs_sr_1/102-3144140-0389701?ie=UTF8&amp;amp;s=books Beautiful Code]).&lt;br /&gt;
* The Collaborative Organization of Knowledge. (With P. Louridas; &#039;&#039;Communications of the ACM&#039;&#039;.&lt;br /&gt;
* Enhancing Educational Services through E-Learning: The case of a Java Randomized Personal Exercise Builder. (With P. Zacharias and M. Vrechopoulos; &#039;&#039;Computer Applications in Engineering Education&#039;&#039;).&lt;br /&gt;
* A Framework for the Static Verification of API Calls. (With P. Louridas; &#039;&#039;Journal of systems and Software&#039;&#039;).&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
[[Category:Private dds]]&lt;/div&gt;</summary>
		<author><name>193.92.228.97</name></author>
	</entry>
</feed>