Proceedings Article10.1109/VLHCC.2017.8103446
Exploring exploratory programming
Mary Beth Kery,Brad A. Myers +1 more
- 01 Oct 2017
pp 25-29
111
TL;DR: This work provides an organized description of what exploratory programming has meant historically and a framework of four dimensions for studying exploratory Programming tasks: applications, required code quality, ease or difficulty of exploration, and the exploratory process.
read more
Abstract: In open-ended tasks where a program's behavior cannot be specified in advance, exploratory programming is a key practice in which programmers actively experiment with different possibilities using code. Exploratory programming is highly relevant today to a variety of professional and end-user programmer domains, including prototyping, learning through play, digital art, and data science. However, prior research has largely lacked clarity on what exploratory programming is, and what behaviors are characteristic of this practice. Drawing on this data and prior literature, we provide an organized description of what exploratory programming has meant historically and a framework of four dimensions for studying exploratory programming tasks: (1) applications, (2) required code quality, (3) ease or difficulty of exploration, and (4) the exploratory process. This provides a basis for better analyzing tool support for exploratory programming.
read more
Chat with Paper
AI Agents for this Paper
Find similar papers on Google Scholar, PubMed and Arxiv
Write a critical review of this paper
Analyze citations of this paper to find unaddressed research gaps
Citations
Managing Messes in Computational Notebooks
Andrew Head,Fred Hohman,Titus Barik,Steven M. Drucker,Robert DeLine +4 more
- 02 May 2019
TL;DR: Code gathering tools, extensions to computational notebooks that help analysts find, clean, recover, and compare versions of code in cluttered, inconsistent notebooks are introduced.
169
What's Wrong with Computational Notebooks? Pain Points, Needs, and Design Opportunities
Souti Chattopadhyay,Ishita Prasad,Austin Z. Henley,Anita Sarma,Titus Barik +4 more
- 21 Apr 2020
TL;DR: It is suggested that data scientists face numerous pain points throughout the entire workflow - from setting up notebooks to deploying to production - across many notebook environments.
166
How Data Scientists Use Computational Notebooks for Real-Time Collaboration
April Yi Wang,Anant Mittal,Christopher Brooks,Steve Oney +3 more
- 07 Nov 2019
TL;DR: How synchronous editing in computational notebooks changes the way data scientists work together compared to working on individual notebooks is reported and several design implications aimed at better supporting collaborative editing in synchronous notebooks are proposed, thus improving efficiency in teamwork among data scientists.
125
Practitioners Teaching Data Science in Industry and Academia: Expectations, Workflows, and Challenges
Sean Kross,Philip J. Guo +1 more
- 02 May 2019
TL;DR: Twenty data scientists who teach in settings ranging from small-group workshops to large online courses found that they must empathize with a diverse array of student backgrounds and expectations and face challenges involving authenticity versus abstraction in software setup, finding and curating pedagogically-relevant datasets, and acclimating students to live with uncertainty in data analysis.
95
In-IDE Code Generation from Natural Language: Promise and Challenges
TL;DR: In this paper , a plugin for the PyCharm IDE implements a hybrid of code generation and code retrieval functionality, and orchestrate virtual environments to enable collection of many user events (e.g., web browsing, keystrokes, fine-grained code edits).
References
Debugging reinvented: asking and answering why and why not questions about program behavior
Amy J. Ko,Brad A. Myers +1 more
- 10 May 2008
TL;DR: The Whyline is a new kind of debugging tool that enables developers to select a question about program output from a set of why did and why didn't questions derived from the program's code and execution.
316
Computational science: ...Error.
TL;DR: E-mails from the Climatic Research Unit (CRU) at the University of East Anglia in Norwich, UK, last year revealed another problem — one described by a CRU employee named “Harry”, who often wrote of his wrestling matches with wonky computer software.
245
Cowboys, ankle sprains, and keepers of quality: how is video game development different from software development?
Emerson Murphy-Hill,Thomas Zimmermann,Nachiappan Nagappan +2 more
- 31 May 2014
TL;DR: Using game development as a starting point for impacting game development, researchers could create testing tools that enable game developers to create tests that assert flexible behavior with little up-front investment.
Design as exploration: creating interface alternatives through parallel authoring and runtime tuning
Björn Hartmann,Loren Yu,Abel Allison,Yeonsoo Yang,Scott R. Klemmer +4 more
- 19 Oct 2008
TL;DR: Techniques to support design exploration for desktop, mobile, and physical interfaces are described, and this work is situated in a larger design space of tools for explorative programming.