Comment by sauercrowd
6 days ago
I really don't think we're doing the tools or the industry any favors/justice by prefixing new terms with `vibe`.
Looking at vibe coding: it suggests you're coding but you only vaguely know what's going on, so the work is the same (coding) but the outcome may or may not be what you want
Why dont we flip it around? We want a term that suggests that a fixed amount of work (coding) to be more efficient/leveraged.
So why dont we call it something like hypercoding, dense engineering, autocode, ...
Some more options (I used AI with a nuanced not-too-lazy prompt, I hope it is okay):
Prompt Engineering / Directed Prompting
Architectural Steering
Spec-Driven Development
Intent-Based Coding
Critical Synthesis
Iterative Refinement
Guided Iteration
Hypothesis-Driven Coding
AI-Assisted Engineering
Cognitive Pair Programming
Dialogic Programming
Structured Prompting for Code (SPC)
Code Shepherding
AI-Assisted Engineering is probably the most descriptive. My favourite are Critical Synthesis and Code Shepherding. Both abbreviate to CS