The programming-process replay was the most prompt-intensive view to develop, requiring 31 prompts to work reliably and handle edge cases¶

Claim · All claims
Evidence · 1 study · design r2 · q2
Currency · newest study 2026 · not yet checked against its sources · not reviewed by a person

Subclaims¶

q2 i? Among the visualizer's views, the programming-process replay required the largest number of prompts (31) to make it work reliably and consistently, display information correctly across tabs and logs, and account for edge cases. → Heidi Taveter and Marina Lepp 2026

Evidence¶

Heidi Taveter and Marina Lepp 2026¶

Heidi Taveter and Marina Lepp. (2026). From Idea to Classroom in Days: Using “Vibe Coding” to Create a Programming Process Visualizer from IDE Activity Logs. https://arxiv.org/abs/2607.24757 doi:10.48550/arxiv.2607.24757

q2 · i? · design · r2

Developer-reported development accounting within the AI-assisted vibe coding workflow: of 207 total Lovable prompts, the replay view required 31, the most of any view, because of reliability, cross-tab consistency, point inspection, and edge-case handling. No effect size is applicable.

"Compared to other views, developing the programming-process replay required the largest number of prompts (31): to make it work reliably and consistently, ensure that information across tabs and logs is displayed correctly, allow the user to inspect points of interest in more detail, and account for edge cases."

Discussion¶

Related Claims¶

• The visualizer's flagging mechanisms flagged all tested logs from cases already known to involve plagiarism while still requiring student-level review — related
• In a five-teacher pilot in a 160-student introductory programming course, teachers valued rapid process-level insight and the pilot drove iterative usability improvements — related
• A graded likelihood detector prompt produced more consistent separation than a binary yes/no detector prompt — related