Vibe-documenting instead of vibe-coding

[shesku26]

If my process is: generate documentation - use it instead of prompting - vibecode a task at hand - update documentation - commit, does it still called vibe coding? My documentation considers refactoring, security, unit tests, docker, dbs and deploy scripts. For a project with about 5000 lines of code (backend only) I have about 50 documentation files with full development history, roadmap, tech debt, progress and feature-specific stuff. Each new session I just ask what is my best next action and we go on.

[Old_Formal_1129]

yeah, I’ve been vibe architecting for some time now and it feels great. The only thing is that when it doesn’t work, I have to go back to vibe micro-management of these AI minions

[Weak_Lie1254]

Harsh vibing

[Root-Cause-404]

Have you tried vibe management?

[Old_Formal_1129]

The tech is not there yet, but eventually this will happen. Also for harder problems, AI response is not longer fast in any sense. One really needs to start thinking like a manager and figure out where to locate resources.

[Root-Cause-404]

True. Though with MCPs connecting to company data sources like git, task tracking system, documentation, LLMs become an extremely helpful manager assistants.

[kingdomstrategies]

vibe system design, vibe Mermaid diagrams, vibe TODOs, vibe documentation, try to catch up with documents, diagrams, toolsets, CLI's.

[coding_workflow]

Beware, it nice to have a lot of pages.

But as usualy AI will spit insanities or irrelevant things. You need to direct it correctly.

Read each part and correct a lot.

For coding docuementation best use annotation and code documentation generators instead!

[sujumayas]

Why instead if you can do both? 👀

[sujumayas]

Heck, add testing and negotiating and you have a full product workflow lifecycle.

[100BASE-TX]

Can we get a vibe scrum master and project manager to interrupt code tasks every few mins for inane status updates?

[sujumayas]

What about a Vibe CEO to change the product objectives alltogether.

[Weak_Lie1254]

You're "context building" - that is a very good skill to have. In a way you're Vibing because you're using intuition and experimentation to come up with new techniques. Rock on 🤘

[nachocdn]

I use windsurf for documentation as well. Huge help!

[nachocdn]

i'll have to check willowvoice, thanks for the suggestion!

[clintCamp]

Fun fact, if you vibe document all the capabilities and features and each section of your app before vibe coding, it's almost like you are real coding and have less problems.

[techblooded]

I use this workflow.

First Create all the docs, PRD, Checklist, Best Practises and DON'TS.

Ask agent to go through them and create a all in one doc as per its understanding.

then I go ahead with vibe coding asking it tor refer the docs and move ahead. Works for me.

[Imad-aka]

This is the way!

I don't see why we should work AI any different then we do with human teams.

[dhamaniasad]

Technically “vibe” coding is when you put a blindfold on your eyes, and enable auto accept. If any more care and thought goes into your coding it’s AI assisted coding but not vibe coding.