There is a distinction drawn between 'vibe coding'—prompting an LLM to generate scripts or apps—and traditional software engineering. Some users view this workflow as 'slop' or merely prompting, lacking the depth of actual problem-solving, while others find it empowering for quick prototypes or hobby projects. This theme reflects broader tensions regarding the changing nature of software development in the age of generative AI.
← Back to Stop Doom Scrolling, Start Doom Coding: Build via the terminal from your phone
The rise of "vibe coding" via mobile-accessible AI agents has sparked a polarizing debate between those who embrace it as a liberating productivity hack and critics who dismiss it as "automated slop." Proponents celebrate the ability to scaffold micro-utilities and learn new frameworks during commutes, arguing that offloading syntax to LLMs transforms the smartphone from a consumption device into a viable development terminal. However, many seasoned engineers contend that merely prompting an AI is a form of "doom-slopping" that lacks the depth of genuine problem-solving, fearing a future where developers can no longer navigate complex codebases without an algorithmic intermediary. This tension highlights a fundamental shift in the industry, as the boundary between traditional software engineering and high-level requirements gathering becomes increasingly blurred.
43 comments tagged with this topic