Code in Context: Keeping Developer Context and Interfaces on Evolving Software

dc.contributor.advisorTanimoto, Steven L.
dc.contributor.advisorTatlock, Zachary
dc.contributor.authorMisback, Edward
dc.date.accessioned2025-08-01T22:19:33Z
dc.date.available2025-08-01T22:19:33Z
dc.date.issued2025-08-01
dc.date.submitted2025
dc.descriptionThesis (Ph.D.)--University of Washington, 2025
dc.description.abstractDespite progress in programming tools and environments, developers still struggle to maintain mental models of the systems they build and the context surrounding their code. This dissertation advances a framework for enhancing program understanding and manipulation for all agents working with a codebase—including developers and automated agents such as large language models (LLMs)—through notes on shared context and high-level representations that are semantically attached and synchronized, i.e., external notes and UIs that stay linked to sections of a program where they are meaningful, with their content updated to remain relevant. I first address the specific case of floating-point error analysis with Odyssey. Odyssey is a workbench for floating-point analysis that transforms an existing low-level, black-box expression improvement tool into a high-level, scaffolded analysis process where users can analyze, generate, and iterate on automated suggestions using their own expertise. Next, considering how contextual information from an Odyssey analysis session might be attached to actual floating-point programs, I explore maintaining semantic connections between document sections and metadata using Magic Markup. This system uses an LLM to "magically" maintain the positions of external notes on an evolving document without write access through semantic anchoring rather than brittle syntactic approaches. Finally, I formalize and implement this approach in Codetations, a VSCode extension that helps developers contextualize documents with rich, interactive notes and tools. Codetations builds on the Magic Markup method to keep notes outside the document while integrating edit-tracking and exposing a rich API for annotations to respond to buffer changes and leverage editor features. In a qualitative evaluation, developers recognize this method as enabling more extensive and useful forms of documentation, and worked examples show the additional context improving code repair performance in LLMs. Together, these systems indicate a practical path by which existing programming systems can begin to offer powerful, developer-customized tools that meet developers' needs for contextual information and high-level analysis.
dc.embargo.termsOpen Access
dc.format.mimetypeapplication/pdf
dc.identifier.otherMisback_washington_0250E_28620.pdf
dc.identifier.urihttps://hdl.handle.net/1773/53500
dc.language.isoen_US
dc.rightsCC BY-SA
dc.subjectComputer science
dc.subject.otherComputer science and engineering
dc.titleCode in Context: Keeping Developer Context and Interfaces on Evolving Software
dc.typeThesis

Files

Original bundle

Now showing 1 - 1 of 1
Loading...
Thumbnail Image
Name:
Misback_washington_0250E_28620.pdf
Size:
4.66 MB
Format:
Adobe Portable Document Format