[D] How do ML engineers view vibe coding?
A viral Reddit thread reveals ML engineers' split views on using AI for probabilistic coding tasks.
A viral thread on the r/MachineLearning subreddit, titled 'How do ML engineers view vibe coding?', has sparked a significant debate within the AI community. The original poster sought to distinguish the experience of ML engineers from traditional software developers when using AI coding assistants like GitHub Copilot or ChatGPT. The term 'vibe coding' colloquially refers to the iterative, prompt-driven process of generating and refining code with AI, which aligns more with the experimental, probabilistic nature of machine learning work compared to building deterministic systems.
Responses from practicing ML engineers revealed a nuanced and divided landscape. A key point of consensus is that AI excels at accelerating boilerplate tasks, such as writing data loading scripts, generating common model architectures, or drafting documentation, freeing engineers for higher-level design. However, many expressed deep skepticism about using AI for core algorithmic work, reasoning that current models often hallucinate APIs, produce subtly incorrect math, or fail to grasp the nuanced trade-offs required for model optimization and debugging, which can actually slow down development.
The discussion underscores a fundamental tension: while AI is a powerful tool for exploration and automation, its probabilistic outputs clash with the need for precision and deep understanding in ML engineering. The thread concluded that 'vibe coding' is a useful supplement but not a replacement for expertise, especially for tasks involving novel research, complex system integration, or performance-critical code. The divide often falls along lines of task complexity and the engineer's experience level.
- The Reddit thread highlights a professional split: some ML engineers use AI for speed on boilerplate tasks (data scripts, docs), while others avoid it for core algorithmic work due to error risks.
- A major concern is AI's 'probabilistic' output clashing with ML's need for precision, leading to hallucinations in APIs, math, or model optimization logic that can slow debugging.
- The consensus is that 'vibe coding' acts as a powerful assistant for exploration and automation but cannot replace deep technical expertise for novel research or complex system design.
Why It Matters
As AI coding tools proliferate, understanding their real utility and pitfalls in specialized fields like ML is crucial for effective adoption and productivity.