Sign inGet started
Paper · arXiv

Where Did the Variability Go? From Vibe Coding to Product Lines by Regeneration

In vibe coding, an emerging AI-driven paradigm, an LLM generates an entire program from a natural language prompt, but what happens to the variability that traditional software engineering carefully builds into code? To answer this question, we conducted an exploratory analysis on 10 vibe coded C/C++ projects, which suggests that there is near zero in-artifact variability, i.e., at compile- and runtime. All variability decisions are resolved at a single new binding time, generation time, the moment the LLM produces the source code. Rather than treating this as a defect to fix, we propose Variability by Regeneration (VbR), to our knowledge the first product line approach in which the LLM a...

AuthorsXhevahire Tërnava
Primary categorycs.SE
Published17 June 2026
Last updated at source8 July 2026
cs.SEcs.AI
Embed this entry
<iframe src="https://silytics.si/embed/item/a6acab4a-1297-44bf-b21f-535b4ea3a994" width="420" height="190" style="border:0" loading="lazy" title="Silytics entry"></iframe>

Free, no tracking. More about feeds and embeds.

Silytics shows public metadata from arXiv and links to the original. Information may be incomplete or out of date. Last refreshed 17 October 2026. Licenses and terms of the original apply to the work itself. Not financial, legal or professional advice.