You are viewing archived messages.
Go here to search the history.

Rebecca Krosnick 2023-02-27 16:56:56

May be of interest to Future of Coding folks as a way to get feedback or share your work.

VL/HCC 2023 (IEEE Symposium on Visual Languages and Human-Centric Computing) is currently soliciting papers (abstracts due April 21, papers due April 28).

VL/HCC 2023: IEEE Symposium on Visual Languages and Human-Centric Computing

The IEEE Symposium on Visual Languages and Human-Centric Computing is the premier international forum for research on this topic. Established in 1984, the mission of the conference is to support the design, theory, application, and evaluation of computing technologies and languages for programming, modeling, and communicating, which are easier to learn, use, and understand by people.

The 2023 symposium is scheduled to take place October 2-6 in Washington, DC, USA. VL/HCC 2023 is 100% Sponsored by IEEE Computer Society Technical Committee on Multimedia Computing (TCMC).

Call for Research Papers


- Abstracts only: April 21, 2023

- Submission deadline: April 28, 2023

  • Rebuttal phase: June 5 - 9, 2023

  • Notification: June 23, 2023

  • Camera-ready: July 14, 2023


We solicit original, unpublished research papers on computing technologies for modeling, programming, communicating, and reasoning, which are easier to learn, use or understand by humans than the current state-of-the-art. Papers should focus on efforts to design, formalize, implement, or evaluate those technologies and languages. This includes technologies intended for general audiences (e.g., professional or novice programmers, or the public) or domain-specific audiences (e.g., people working in business administration, production environments, healthcare, urban design or scientific domains). Empirical papers that validate current proposed solutions with rigorous scientific means (i.e., empirical studies, controlled experiments, rigorous case studies, etc.) are also welcome.

Areas of interest include, but are not limited to:

  • Visual languages: Novel visual languages, Design, evaluation, and theory of visual languages and applications, Development of systems for manipulating and interacting with diagrammatic representations

  • Human aspects and psychology of software development and language design, such as supporting inclusion and diversity in programming

  • End-user development: End-user development, adaptation and programming, Creation and evaluation of technologies and infrastructures for end-user development

  • Crowdsourcing design and development work

  • Representations: Novel representations and user interfaces for expressing computation, Software, algorithm and data visualization

  • Modeling: Model-driven development, Domain-specific languages, including modeling languages, Visual modeling of human behavior and socio-technical systems

  • Thinking more deeply about code: Computational thinking and Computer Science education, Debugging and program understanding, Explainable ML/AI

If you are not sure if your paper is a good fit for VL/HCC, feel free to email the PC Co-chairs (see “Contact” below). We welcome those new to the VL/HCC community to submit!

SPECIAL EMPHASIS FOR 2023: Low-Code / No-Code Development

This year’s special topic is “Low-Code / No-Code Development”. This development paradigm enables the creation and deployment of fully functional applications using visual abstractions and interfaces and requiring little or no procedural code. This way, users are empowered to create software applications for constrained domains, even if they lack a programming background. This year, we especially welcome papers at VL/HCC that design, build, or evaluate any aspects of low-code and no-code solutions.


We invite two kinds of papers:

  • full-length research papers, up to 8 pages - plus unlimited additional pages containing only references and/or acknowledgements

  • short research papers, up to 4 pages - plus unlimited additional pages containing only references and/or acknowledgements

Papers must be submitted using the IEEE two-column conference paper format. Be sure to use the current IEEE conference paper format (which was updated in 2019), and to select the “US letter” template:

Papers should be submitted via the EasyChair system (

To facilitate the assigning of papers to reviewers, we require paper abstracts to be submitted via EasyChair at least 1 week prior to the paper submission deadline (see Important Dates below). The abstract must be kept up to date such that it matches exactly the abstract in the submitted paper. The abstract must be no longer than 250 words.

All accepted papers, whether full or short, should be complete, self-contained, archival contributions. Contributions from full papers are more extensive than those from short papers. Note that some full paper submissions may be accepted as short papers if reviewers deem contributions to be comparable in size to a short paper. Work-in-progress, which has not yet yielded an archival contribution, should be submitted to the Posters/Showpieces category. All submissions will be reviewed by members of the Program Committee in a double-blind review process. Authors will then receive the reviews for their submissions and will be able to answer them in a rebuttal phase. Only after this step the PC will make a final decision about the acceptance of the submissions. Submissions and reviews for the technical program are managed with EasyChair. At least one author of each accepted paper is required to register for VL/HCC 2023 and present the paper at the conference. There will be a virtual presentation option in case of travel restrictions. IEEE reserves the right to exclude a paper from distribution after the conference, including IEEE Xplore Digital Library, if the paper is not presented by the author at the conference.

The proceedings of IEEE VL/HCC are published in digital form by the IEEE Computer Science Society and archived in the IEEE Digital Library with an official ISBN number. Accepted papers will be available to conference attendees via the IEEE Open Preview program in the IEEE Xplore Digital Library (


We follow a double-blind reviewing process. Both authors and reviewers are expected to make every effort to honor the double-blind reviewing process. In case of questions, please contact the Program Chairs. Authors should ensure that the submission can be evaluated without it being obvious who wrote the paper. This means leaving author names off the paper and using terms like “previous research” rather than “our previous research” when describing background. However, do not hide previous work – papers must still reference all relevant research using full (non-anonymized) citations, including the author’s own prior work, so that reviewers can evaluate novelty. Please reference your own prior work in the third-person just like you would do for any other related work (e.g., avoid “As described in our previous work [10], … ” and instead write something like “As described by [10], …“). It is also important that authors specify all conflicts of interest with potential reviewers during the submission phase.

Reviewers should not undertake any investigation that might lead to the revealing of authors’ identity. If identities are inadvertently revealed, please contact the Program Chairs.

The Program Chairs will check all submissions for obvious signs of lack of anonymity and may ask authors to make changes and resubmit the paper within three days of the submission deadline. Only changes to resolve anonymity issues will be permitted.


Papers are expected to support their claims with appropriate evidence. For example, a paper that claims to improve programmer productivity is expected to demonstrate improved productivity; a paper that claims to be easier to use should demonstrate increased ease of use.

However, not all claims necessarily need to be supported with empirical evidence or studies with people. For example, a paper that claims to make something feasible that was clearly infeasible might substantiate its claim through the existence of a functioning prototype.

Moreover, there are many alternatives to empirical evidence that may be appropriate for justifying claims, including analytical methods, formal arguments or case studies. Given this criterion, we encourage potential authors to think carefully about what claims their submission makes and what evidence would adequately support these claims. In addition, we expect short papers to have less comprehensive evaluation than long papers.


PC Co-Chairs:

  • Philip Guo (University of California San Diego, United States)

  • Esther Guerra (Universidad Autónoma de Madrid, Spain)

  • Contact email:

Ivan Reese 2023-02-27 17:24:31

Awesome. Thank for sharing this CFP here @Rebecca Krosnick!

Jason Morris 2023-02-28 05:59:52

I'm not sure how these things work, but I have a paper that has been proposed and is not yet accepted for publication at another venue. Can you submit the same paper to multiple places, and give it to the first to accept? Or is your paper locked as soon as you submit it, until it is rejected?

Duncan Cragg 2023-02-28 09:05:30

It would be uncool to present the same thing in two places, but it's probably OK to submit to several conferences then pick the best offer. I'm not an academic though, so.

Duncan Cragg 2023-02-28 09:12:52

Actually, given the peer review process, which will involve the same community or even the same reviewers, it's going to look bad submitting to multiple conferences when they're on similar topics. So I'm backtracking a bit on my ill-informed advice! 😂

Duncan Cragg 2023-02-28 09:13:59

Teach me not to post to a thread just to get ongoing notifications 😁

Rebecca Krosnick 2023-02-28 17:46:33

Hi Jason Morris I’m sorry for the delay! I’m not 100% sure, and I don’t want to give you the wrong answer. I think you could contact the program committee chairs if you want to check.

PC Co-Chairs:

  • Philip Guo (University of California San Diego, United States)

  • Esther Guerra (Universidad Autónoma de Madrid, Spain)

  • Contact email:

Joshua Horowitz 2023-03-01 00:36:56

Jason Morris: It’s always a good idea to get in touch with the chairs, but FWIW, I am comfortable saying that it is not considered acceptable to submit a paper to multiple venues simultaneously.

See, e.g., this discussion.

Here’s the basic syllogism:

  • You should only submit a paper to a venue if you can commit to publish there if accepted. (Otherwise, you waste the reviewers time.)
  • You cannot publish a paper in multiple venues.
  • Therefore, you cannot submit a paper to multiple venues.
Jason Morris 2023-03-01 00:57:54

I guess I should be grateful that's not how job applications work. God everything about academic publishing is stupid.

Joshua Horowitz 2023-03-01 02:33:59

Jason Morris I won’t argue with that.

Rebecca Krosnick 2023-03-02 11:01:26

Jason Morris, fwiw there is a posters/demos track with a deadline of June 28, in case that better matches your timeline:

Also idk for sure, but I think you may be able to submit your work even if it was already accepted elsewhere. The call says this:

Submitters may opt to have publishable submissions omitted from the proceedings, in case they wish to avoid any possibility of a prior-publication issue with a future archival publication. If this is the case, please email the PC chairs.

Not exactly your situation, but related.

Jason Morris 2023-03-02 15:06:33

Thanks, Rebecca.

Gabriel Grinberg 2023-03-02 20:33:02

@Rebecca Krosnick Thanks for sharing!

Any ideas if the call for posters/posters is already open? followed the instructions seeing the following message on

Paper submission for VL/HCC 2023 is closed.

Rebecca Krosnick 2023-03-02 23:52:48

@Gabriel Grinberg , guessing it’s not open yet but you could contact the program chairs to let them know the message you’re seeing and ask when the site will start accepting submissions

PC Co-Chairs:

Philip Guo (University of California San Diego, United States)

Esther Guerra (Universidad Autónoma de Madrid, Spain)

Contact email:

Gabriel Grinberg 2023-03-03 07:43:00


Nick Arner 2023-02-28 17:21:41

Wrote something recently on the idea of using LLMs as part of in-the-loop software assistants:

Aaron Larner 2023-02-28 20:07:13

Thanks for sharing! I’ve been thinking about how LLMs can be used to assist in “bootstrapping” projects that normally require complex software. I think there’s value for a novice, or even expert to be able to use a chat interface to define the rough requirements and then the output of that conversation would be a starter or template file that could then be opened in the software and further edited / tweaked. I think you touched on some a key point: complex software is complex because it solves complex problems. Chat interfaces are not best suited to do the complex stuff, but they can help us do the simple stuff, that previously may have been difficult due to complicated UI.

Jason Morris 2023-02-28 23:57:42

Here's a little gif of the new scenario editor in the version 1.4 of Blawx I released today. It allows the user to make fully-, partially-, or un-ground statements that are true, false, or unknown , answers the query with natural language explanations that set out the assumptions being used for unknowns, and then recommends additional fact statements that would be relevant to finding additional conclusions that are not based on assumptions. It's aimed at encoding statutes and regulations in such a way as to allow those encodings to be made, or at least validated, by lawyers and other non-programmers. Feedback welcome. The new release is up at now.

Mariano Guerra 2023-03-02 00:02:47

I just integrated the newly announced ChatGPT API into GlooData, here's a video showing how to use it to schedule slack messages with interesting facts about home appliances.

🕰️ 2022-11-06 01:48:26


Ryo Hirayama 2023-03-02 07:37:36

I've released a POC of my visual editor. You can try it at (You should wait for up to 10 seconds on the first load to fetch and compile a Wasm binary. If it seems crash before running, reloading without caches or using other devices would help). Open the editor by clicking the "Fibonacci" button, then hover or click anywhere within the code, and use arrow keys to move around the cursor word by word.

It's really lightweight to rendering the editor in 30fps or more with low cpu usage and it's throttled to 1fps while you aren't operating the input devices. If you have a cheap laptop or tablet, you should also try the editor on it, and it'll work nicely even on not powerful processors.

You may notice the quality of font rendering is not good. It varies on what browser you use, and zooming in the page should improves the readability. Although I don't mainly use apple devices, it's best and beautiful on their devices. I'm finding a way to fix this problem but not with the top priority.

Based on this POC, I plan to add these features in this order:

  • Rendering the code with syntax sugars
  • Inlay-hints and hover popups to show the inferred type of an expression and any compiler messages

  • ▶ button to run the code

  • Dragging single or multiple expressions to move it to another place including other files

  • Structural editing at cursor

Josh Justice 2023-03-03 21:59:39

Hey folks, I have been hanging around Future-of-Code-like communities for a few years, trying to figure out what I want my focus to be. I’ve finally figured it out, and I made a demo video to share with y’all about what I’m working on.

It’s a web and mobile app for tracking your personal information, including allowing end users to configure buttons and actions to customize their workflow. It’s not groundbreaking research, but it does enable end users to create interactive software anywhere they are. I’ve been able to replace at least four apps I previously used with “boards” I’ve configured in this app. I plan to open-source it and set up a free open-registration server soon.

Here’s the demo if anyone would like to take a look!

Tudor Girba 2023-03-03 22:08:37

Nice. And the red Smalltalk-80 book is prominently in the background 🙂.

Josh Justice 2023-03-03 22:52:25

Had to leave those Easter eggs in for those in the know 😃

Kartik Agaram 2023-03-04 02:35:17

I really like the problem you're tackling, I've been aiming in a similar direction, though in a radically different and differently radical way.

I have a couple of questions that'll likely answer themselves once your app is published:

  • What sort of stack are you using? I'm guessing some sort of Javascript. What sort of upgrade burden do you anticipate for someone self-hosting?
  • What do you use for data storage? That's often a significant maintenance burden, in my experience.
  • Will the mobile apps work with arbitrary servers, or will anyone self-hosting need to put their own copies of the app through App Store review?
Jack Rusher 2023-03-04 07:02:00

love the malleability 🙂

Josh Justice 2023-03-04 11:36:25

Kartik Agaram Great questions.

The architecture of the app is thick clients talking to a RESTful HTTP backend with JSON. I’m using this both for ease of initial development and ease of future development: if the frontend or backend become restrictive, there is the option for me or others to write new or additional frontends/backends in different technologies.

The backend is currently a “normal” Ruby on Rails API backed by Postgres. To support self-hosting, I will want to set it up to be easy to spin up new instances on Docker or Heroku (which is where I currently host it). Hosting the app isn’t for non-programmers/non-IT people, due to the limitations of the underlying technologies. But this question has gotten me thinking of the tradeoffs of other backend technologies: Golang would allow shipping a single binary, but does not allow folks to easily verify the code included in that binary.

The frontend is built on React Native, using the react-native-web package to also target web with the same frontend codebase. I want to set up the mobile clients to be configurable to access any backend, so that you don’t have to publish your own mobile app, but you have the option to if you make feature changes to it. There’s some developer burden keeping it up-to-date (it’s a heavy stack). For someone hosting, the frontend web updates would hopefully be as simple as keeping Node up-to-date and running an npm install . TBD how much interest the project gets; if/when some folks start self-hosting I know I’ll need to put more attention to ensuring they have a good experience.

Any followup thoughts or questions you have based on that would be welcome! Thanks.

🕰️ 2023-02-11 21:27:59


Marcel Weiher 2023-03-05 13:59:24

Great Episode! Lots to process, definitely have to re-read NSB sometime soon. Possibly of interest, the ~20 year NSB retrospective: