Back to Empathize

empathize/related-work

Summary

  1. [[#^preliminary|Preliminary Literature Review]]
    1. Live programming environments
    2. Academic Reviewing
    3. Academic Publishing
    4. Reproducibility
    5. Markup formats
  2. Review Existing interfaces
    1. Overleaf
    2. Obsidian
    3. Zotero
    4. Google Docs / Microsoft Word
    5. Medium
    6. HTML/JS
    7. Jupyter Notebook
      • Quarto
      • Marimo
    8. VSCode
  3. Review Communities
    1. Wiki, Wikipedia
    2. Journals
    3. Research Labs
  4. Interview
    1. Academic Publishers
    2. Authors
    3. Conference Paper Chairs

Preliminary Literature Review ^preliminary

For each work, determine the following:

  1. Stakeholders
    1. What groups of people does this work study?
    2. Where is this work published?
  2. Preliminary work
    1. Did they do any preliminary studies?
    2. What related work did they mention?
  3. Problems
    1. What problems did they isolate?
    2. What problems are they targeting?
  4. Solutions
    1. What solutions did they propose?
    2. Did they implement them? How?
  5. Evaluation
    1. How was this work evaluated?
  6. Remaining work
    1. What problems are left unsolved?

Isaac’s Papers

Todo:

TABLE 
  papis-title AS "Title",
  readers     AS "Readers"
FROM "Empathize/Sources"
WHERE
  contains(readers, "Isaac")
  AND (
    length(stakeholders) = 0
    OR length(preliminary)  = 0
    OR length(problems)     = 0
    OR length(solutions)    = 0
    OR length(evaluation)   = 0
    OR length(remaining)    = 0
  )
SORT papis-year ASC

Done:

TABLE 
  papis-title AS "Title",
  readers     AS "Readers",
  date AS "Date"
FROM "Empathize/Sources"
WHERE
  contains(readers, "Isaac")
  AND length(stakeholders) > 0
  AND length(preliminary)  > 0
  AND length(problems)     > 0
  AND length(solutions)    > 0
  AND length(evaluation)   > 0
  AND length(remaining)    > 0
SORT papis-year ASC

First batch notes:

  1. Some seemed better than others, there’s not a good way to indicate this currently
  2. Themes:
    1. Lowering the barrier of entry for editing, giving access to non-expert stakeholders
      1. I remember from the Virtual DSLs Papers [[Empathize/Sources/hanna-keith2002-interactive-visual-functional-programming/Notes|Interactive Visual Functional Programming]]
        1. Business professionals use spreadsheets, not ideal (90%)
      2. Where can we better justification that this is needed?
    2. Collaboration
      1. Mechanisms through which one can facilitate collaborative editing
      2. How editing systems affect how people collaborate
        1. (wikipedia, google docs)
    3. Theoretically ideal PLs are not easily adoptable
    4. NEED MORE ABOUT WRITING TEXT
    5. AI INTEGRATION IN TEXT WRITING INTERFACES
  3. Let’s take some sources from https://web.engr.oregonstate.edu/~burnett/vpl.html

Second Run:

  1. Still no good way to evaluate importance of papers
  2. Themes:
    1. Visual Representations of Text
      1. [[decoration.pdf|Code Mirror]] decorations discuss different ways that program aspects can be visualized
      2. [[asenov-et-al.-2016-the-effect-of-richer-visualizations-on-code-comprehension.pdf|Richer Visualizations]] empirically evaluate the way visuals affect code comprehension
      3. These papers explore the ways that users interact with and comprehend an editor’s visual display
    2. Evaluation of Editors
      1. [[roberts-and-moran-1983-the-evaluation-of-text-editors-methodology-and-empirical-results..pdf|Original ]] and [[borenstein-1985-the-evaluation-of-text-editors-a-critical-review-of-the-roberts-and-morgan-methodology-based-on-new.pdf|the review]] discuss a particular methodology for evaluating text editors
      2. Evaluates editors for both novice and expert users, and discuses the manner in which novices learn how to use text editors
    3. Alternative Editing Modalities
      1. [[chugh-et-al.-2016-programmatic-and-direct-manipulation-together-at-last.pdf|Programmatic and direct manipulation]] and [[burckhardt-et-al.-2013-it-s-alive-continuous-feedback-in-ui-programming.pdf|TouchDraw live programming]]
        1. Similar to livelits, manipulate program by interaction with GUI
      2. [[laban-et-al.-2024-beyond-the-chat-executable-and-verifiable-text-editing-with-llms.pdf|LLM editing]]
        1. Investigating editing systems alongside a LLM
      3. [[rosenberg-et-al.-2024-drawtalking-building-interactive-worlds-by-sketching-and-speaking.pdf||Drawtalking]]
        1. Natural language interface in which genAI output accompanies spoken word and sketches on a live campus
  3. Stakeholders:
    1. What groups of people does this work study?
      1. non-expert programmers
        1. [[Empathize/Sources/hanna-keith2002-interactive-visual-functional-programming/Notes|Interactive Visual Functional Programming]]
        2. [[Empathize/Sources/roberts-teresa1983-the-evaluation-of-text-editors-methodology-and-empirical-results./Notes|Evaluation of text editors, methodology and empirical results]]
        3. [[elliott-2007-tangible-functional-programming.pdf|Tangible Functional Programming]]
      2. Data Scientists
        1. [[wang-et-al.-2024-don-t-step-on-my-toes-resolving-editing-conflicts-in-real-time-collaboration-in-computational-noteb.pdf|Don’t step on my toes: Resolving editing conflicts in real-time collaboration in computational notebooks]]
        2. [[clarke-et-al.-2021-appyters-turning-jupyter-notebooks-into-data-driven-web-apps.pdf|Appyters]]
      3. Collaborative Teams
        1. [[adams-et-al.-2025-grove-a-bidirectionally-typed-collaborative-structure-editor-calculus.pdf|Grove]]
        2. [[wang-et-al.-2024-don-t-step-on-my-toes-resolving-editing-conflicts-in-real-time-collaboration-in-computational-noteb.pdf|Don’t step on my toes: Resolving editing conflicts in real-time collaboration in computational notebooks]]
        3. [[yim-et-al.-2016-google-docs-in-the-classroom-a-district-wide-case-study.pdf|Google docs in the classroom: A district-wide case study]]
  4. Where is this work published?
    1. Wide range of venues, but primarily HCI conferences and journals, as well as a few texts oriented towards a more general populace.
  5. Problems:
    1. The main problems that the above papers address are:
      1. Lack of editor evaluation methodology
        1. [[roberts-and-moran-1983-the-evaluation-of-text-editors-methodology-and-empirical-results..pdf|original method]]
        2. [[borenstein-1985-the-evaluation-of-text-editors-a-critical-review-of-the-roberts-and-morgan-methodology-based-on-new.pdf|review]]
      2. Lack of study of the effect of code presentation/visualization
        1. [[asenov-et-al.-2016-the-effect-of-richer-visualizations-on-code-comprehension.pdf |Richer]]
        2. [[Empathize/Sources/codemirror-decoration-example/Notes|Codemirror decoration]]
      3. Formalisms around collaboration
        1. [[adams-et-al.-2025-grove-a-bidirectionally-typed-collaborative-structure-editor-calculus.pdf|Grove]]
      4. Introduction of new editing modalities
        1. See 3 from themes
    2. The solutions to these generally consist of the introduction of methodologies or experimentation where it is lacking
  6. Misc.
    1. Lots of papers are concerned with the presentation of visual materials
      1. Haven’t found as many recent papers talking about pure text editing
      2. Similarly, lots of editing papers are focused primarily on a programming context, which might not necessarily be the most applicable always
      3. There’s a big difference between general purpose editing and editing a program.
    2. Papers involving visual editing systems are primarily block based

Gregory’s Papers

Todo:

TABLE 
  papis-title AS "Title",
  papis-year AS "Year",
  readers     AS "Readers"
FROM "Empathize/Sources"
WHERE
  contains(readers, "Gregory")
  AND (
    length(stakeholders) = 0
    OR length(preliminary)  = 0
    OR length(problems)     = 0
    OR length(solutions)    = 0
    OR length(evaluation)   = 0
    OR length(remaining)    = 0
  )
SORT papis-year ASC

Done:

TABLE 
  papis-title AS "Title",
  readers     AS "Readers"
FROM "Empathize/Sources"
WHERE
  contains(readers, "Gregory")
  AND length(stakeholders) > 0
  AND length(preliminary)  > 0
  AND length(problems)     > 0
  AND length(solutions)    > 0
  AND length(evaluation)   > 0
  AND length(remaining)    > 0
SORT papis-year ASC

Yet to be claimed:

TABLE 
	papis-title AS "Title",
	papis-year AS "Year",
	papis-url AS "Links"
FROM "Empathize/Sources"
SORT papis-year ASC
WHERE length(readers) = 0

Add april wang work on narratives in computational notebooks