The International Conference on the Art, Science, and Engineering of Programming is a new conference focused on programming topics including the experience of programming. We have named it ‹Programming› for short. ‹Programming› 2019 is the third edition of the conference. ‹Programming› seeks for papers that advance knowledge of programming on any relevant topic, including programming practice and experience.
In order to present at ‹Programming› 2019, papers must be submitted to the first, second or third 2019 issue of that journal (timeline).
Conference DayWed 3 AprDisplayed time zone: Amsterdam, Berlin, Bern, Rome, Stockholm, Vienna change
11:00 - 12:30
|Separating Use and Reuse to Improve Both|
Hrshikesh Arora, Marco ServettoVictoria University Wellington, New Zealand, Bruno C. d. S. OliveiraThe University of Hong Kong, Hong KongLink to publication DOI Pre-print
|Clafer: Lightweight Modeling of Structure, Behaviour, and Variability|
Paulius JuodisiusIT University of Copenhagen, Denmark, Atrisha SarkarUniversity of Waterloo, Canada, Raghava Rao MukkamalaDepartment of Technology, Kristiania University College, Norway, Michal AntkiewiczUniversity of Waterloo, Canada, Krzysztof CzarneckiUniversity of Waterloo, Canada, Andrzej WąsowskiIT University of Copenhagen, DenmarkLink to publication DOI Pre-print
|Shallow EDSLs and Object-Oriented Programming: Beyond Simple Compositionality|
Weixin ZhangThe University of Hong Kong, Hong Kong, Bruno C. d. S. OliveiraThe University of Hong Kong, Hong KongLink to publication DOI Pre-print
14:30 - 15:30
|Exploratory and Live, Programming and Coding: A Literature Study Comparing Perspectives on Liveness|
Patrick ReinHasso Plattner Institute, Germany, Stefan RamsonHasso Plattner Institute, Germany, Jens LinckeHasso Plattner Institute, University of Potsdam, Germany, Robert HirschfeldHasso-Plattner-Institut (HPI), Germany, Tobias PapeHasso Plattner Institute, GermanyLink to publication DOI Pre-print
|Babylonian-Style Programming: Design and Implementation of an Integration of Live Examples into General-purpose Source Code|
David RauchHasso Plattner Institute, Germany, Patrick ReinHasso Plattner Institute, Germany, Stefan RamsonHasso Plattner Institute, Germany, Jens LinckeHasso Plattner Institute, University of Potsdam, Germany, Robert HirschfeldHasso-Plattner-Institut (HPI), GermanyLink to publication DOI Pre-print
16:00 - 17:00
|Out-Of-Place Debugging: a Debugging Architecture to Reduce Debugging Interference|
Matteo MarraVrije Universiteit Brussel, Guillermo PolitoUniv. Lille, CNRS, Centrale Lille, Inria, UMR 9189 - CRIStAL - Centre de Recherche en Informatique Signal et Automatique de Lille, Elisa Gonzalez BoixVrije Universiteit Brussel, BelgiumLink to publication DOI Pre-print
|Concrete Syntax with Black Box Parsers|
Research PapersLink to publication DOI Pre-print
Conference DayThu 4 AprDisplayed time zone: Amsterdam, Berlin, Bern, Rome, Stockholm, Vienna change
11:00 - 12:30
|Comprehensive Multiparty Session Types|
Andi BejleriIBM GBS, Frankfurt, Germany, Elton DomnoriCanadian Institute of Technology, Tirana, Albania, Malte VieringTU Darmstadt, Germany, Patrick EugsterUniversita della Svizzera Italiana, Switzerland, Mira MeziniTU Darmstadt, GermanyLink to publication DOI Pre-print
|Semantic Query Integration With Reason|
Philipp SeiferUniversity of Koblenz-Landau, Germany, Martin LeinbergerUniversity of Koblenz-Landau, Germany, Ralf LaemmelUniversity of Koblenz-Landau, Germany, Steffen StaabUniversity of Koblenz-Landau and University of Southampton, GermanyLink to publication DOI Pre-print
|One Monad to Prove Them All|
Sandra DylusUniversity of Kiel, Germany, Jan ChristiansenFlensburg University of Applied Sciences, Germany, Finn TeegenUniversity of Kiel, GermanyLink to publication DOI Pre-print
14:00 - 15:30
|Distributed Reactive Programming for Reactive Distributed Systems|
Florian MyterVrije Universiteit Brussel, Belgium, Christophe ScholliersUniversiteit Gent, Belgium, Wolfgang De MeuterVrije Universiteit BrusselLink to publication DOI Pre-print
|Event Loops as First-Class Values: A Case Study in Pedagogic Language Design|
Joe Gibbs PolitzUniversity of California San Diego, United States, Benjamin LernerNortheastern University, United States, Sorawee PorncharoenwaseBrown University, United States, Shriram KrishnamurthiBrown University, United StatesLink to publication DOI Pre-print
|ParaSail: A Pointer-Free Pervasively-Parallel Language for Irregular Computations|
Tucker TaftAdaCore, United StatesLink to publication DOI Pre-print
16:00 - 17:00
|Applications of Multi-view Learning Approaches for Software Comprehension|
Amir SaeidiUtrecht University, Netherlands, Jurriaan HageUtrecht University, Netherlands, Ravi KhadkaUtrecht University, Netherlands, Slinger JansenUtrecht University, NetherlandsLink to publication DOI Pre-print
|Entombed: An Archaeological Examination of an Atari 2600 Game|
Research PapersLink to publication DOI Pre-print
Call for Papers
The Art, Science, and Engineering of Programming accepts papers that advance knowledge of programming. Almost anything about programming is in scope, but in each case there should be a clear relevance to the act and experience of programming. Additionally, papers must be written in a scholarly form. Scholarly works are those that describe ideas in the context of other ideas that are already known, so to contribute to the systematic and long-standing chaining of knowledge. Papers that fail to properly contextualize the work will not be considered.
We accept descriptions of work under different perspectives:
Art: knowledge and technical skills acquired through practice and personal experiences. Examples include libraries, frameworks, languages, APIs, programming models and styles, programming pearls, and essays about programming.
Science (Theoretical): knowledge and technical skills acquired through mathematical formalisms. Examples include formal programming models and proofs.
Science (Empirical): knowledge and technical skills acquired through experiments and systematic observations. Examples include user studies and programming-related data mining.
Engineering: knowledge and technical skills acquired through designing and building large systems and through calculated application of principles in building those systems. Examples include measurements of artifacts’ properties, development processes and tools, and quality assurance methods.
Independent of the type of work, the journal accepts submissions covering several areas of expertise, including but not limited to:
- General-purpose programming
- Distributed systems programming
- Parallel and multi-core programming
- Graphics and GPU programming
- Security programming
- User interface programming
- Database programming
- Visual and live programming
- Data mining and machine learning programming, and for programming
- Interpreters, virtual machines, and compilers
- Modularity and separation of concerns
- Model-based development
- Metaprogramming and reflection
- Testing and debugging
- Program verification
- Programming education
- Programming environments
- Social coding
Upon submission, authors are requested to state what type of paper they are submitting and what areas of expertise are covered by the paper. These two classifications, combined, are used to select reviewers and to apply suitable assessment criteria for the papers. They are not used beyond that purpose. Misclassification by the authors may lead to negative assessments from reviewers.
The following criteria are used when evaluating submitted papers:
- Novelty and Importance: The paper presents new insights or results, and contributes significantly to the advancement, analysis, or synthesis of knowledge in the field.
- Scholarship and Clarity: The paper places its ideas and results appropriately and clearly within the context established by previous research in the field.
More specific criteria for assessing papers depends on the type of the paper:
- Papers submitted as “The Art” should include a very solid contextualization of the work, and, when applicable, they should include the artifacts themselves.
- Papers submitted as “Science” should describe the methods or formalisms in detail, as well as any data and scripts used to analyze it.
- Papers submitted as “Engineering” should present the methods in detail, unveil results that are clearly better than some accepted baseline, and include the artifacts used to reach the conclusions.
Artifacts are recommended, but not required, for the initial submission. Depending on the papers, reviewers may take the existence of artifacts as a positive signal about the work. Also depending on the papers, artifacts may be required as a condition for publication.
There are two rounds of review. The first round assesses the papers according to the quality criteria stated above, and results in the selection of a subset of submissions that are either accepted as-is or are deemed potentially acceptable. All other papers are rejected. Authors of potentially acceptable papers are requested to improve specific aspects of the research and the paper. Authors are given a specified period of time to perform the revisions and re-submit the paper. During the second and final reviewing round, the same reviewers assess how well the revision requests have been addressed by the authors, and whether the final paper maintains or improves the level of contribution of the original submission. Revisions that significantly lessen the contribution of the work or that fail to adequately address the reviewers’ original concerns will result in the paper’s rejection.
Papers rejected in either the first or second phases may be resubmitted one more time to the journal. The resubmission will be treated as a new submission, and the paper may be assigned to new reviewers. After a second rejection, subsequent submissions of the same paper will be desk-rejected.
Information for Authors
Use the the online submission system at EasyChair.
The template is also available in Overleaf.
Papers must be written in English using high standards of writing. Papers that show poor mastery of the English language will be rejected without review.
The main part of the paper should not exceed 22 pages (in the provided style), but there is no limit for bibliography and appendices. The page limit for the main part of the paper is in place in order to keep the paper on focus and to avoid overloading the reviewers. Authors are encouraged to move important details to appendices, which may be consulted by the reviewers. In some cases, if authors feel that the main part requires substantially more pages, they should explain the reasons why in the additional comments field of the submission form; examples of these cases may include papers with substantial source code listings, and essays. Papers whose length is incommensurate with their contribution will be rejected.
The submission is required to contain an ACM subject classification.
Each submission must be accompanied by a plain-language abstract of up to 500 words that presents the key points in the paper in a manner understandable by experienced practitioners and researchers in nearby disciplines. The abstract should avoid mathematical symbols whenever possible, and it must address the following:
- Context: What is the broad context of the work? What is the importance of the general research area?
- Inquiry: What problem or question does the paper address? How has this problem or question been addressed by others (if at all)?
- Approach: What was done that unveiled new knowledge?
- Knowledge: What new facts were uncovered? If the research was not results oriented, what new capabilities are enabled by the work?
- Grounding: What argument, feasibility proof, artifacts, or results and evaluation support this work?
- Importance: Why does this work matter?
NOTE: The absence of an abstract conforming to this specification is grounds for the rejection of the paper without review.
Submitted papers must present original work made by the authors, must not overlap significantly with the authors’ previously published work, and must not be under review on another journal or conference.
Currently, review uses a traditional process where author names are visible to reviewers. Submissions do not need to be anonymized to hide author names.