A discussion questioning terminology for software that is not open-source but provides complete prompts allowing users to recreate its functionality themselves. The author proposes the term 'hot-source' as a potential label.
A developer advocate at Pinecone uses the analogy of mechanical watch mechanisms—mainsprings, winding, and resistance—to explain how misleading terminology (like 'watermark' for Claude content detection) shapes public misunderstanding of technical systems and drove backlash against Anthropic's decision.
The article draws a parallel between how 'Internet dating' evolved from a stigmatized niche practice to the default 'dating' experience, predicting 'vibe coding' will similarly become just 'coding' as AI assistance becomes universal. As AI tools improve and all coding becomes AI-assisted, the specialized terminology will fade, making today's distinctions between human-centric and AI-driven development obsolete.
A developer argues against calling careful, meticulous programmers 'artisanal' because the term implicitly devalues engineering principles like care and precision. The author contends that terminology matters: those who prioritize reliability and deep code understanding should be called engineers, while faster, less careful developers might better fit other titles like craftsmen.