Charles Ma, software engineer at Chronosphere, said his team takes a similar layered approach. “Many of our engineers use tools like Cursor and Claude Code. We even encourage their use via a usage leaderboard,” he said. “However, we treat them as assistants, not replacements. Our code review process still applies to any production code, and we don’t tend to connect many if any external tools to [AI].”
What is a typical vibe coding workflow or life cycle?
There’s no single blueprint for vibe coding. It flexes depending on the goal, the organization, and the level of structure applied. But two of the practitioners we spoke to offered their somewhat different takes. Typedef’s Pardalis described an agile, creative four-step process:
- Exploration: Define “the vibe: the tone, purpose, and constraints.”
- Shaping: Build and refine “a working prototype.”
- Grounding: Add structure and data integrity.
- Operationalizing: Apply “versioning, evaluation, and governance.”
“At Typedef,” he said, “we think of this as the evolution from prompting to pipelining.”
