What's your actual vibecoding workflow right now?
Summary
The post inquires about current workflows for vibecoding and AI engineering, inviting comparison of tools like Codex, Claude Code, and n8n to optimize the development process from idea to software.
Similar Articles
I vibecoded something engineers are starring in github
The author announces iai-mcp, a local memory tool for Claude Code that retains context across sessions, and reflects on the positive community feedback and rapid iteration following its GitHub release.
@MaximeRivest: Too may software engineers look down on vibe coding, this chart is good at showing when to use which. We have jagged ex…
A commentary on how software engineers should recognize when they are engaging in 'vibe coding' (AI-assisted coding) and that there is jagged expertise, similar to models, in development practices.
Vibe coding and agentic engineering are getting closer than I'd like
Simon Willison reflects on how vibe coding and agentic engineering are converging in his own workflow, raising concerns about code review responsibilities as AI coding agents like Claude Code become increasingly reliable. He explores the ethical tension between trusting AI-generated code in production and maintaining software engineering standards.
How Do We Stop Vibe Coding?
The article discusses the rise of 'vibe coding' using AI agents, its risks to code quality and developer understanding, and calls for rethinking software engineering practices to move beyond merely generating code from intent.
@FeifanZ: am I missing something, or are dynamic workflows just vibe-coding with worse observability?
FeifanZ questions whether dynamic workflows in Claude Code are essentially vibe-coding with worse observability, referencing Claude's announcement of the feature as a research preview for complex tasks.