9Vibe coding can build your pipeline. It can't explain it six months laterSeems like a skill issue. You could have had it create documentation along the way. The idea that prompts can't be versioned or iterated is patently false. Anything in the repo can be versioned.hrm, there's tons of tools to do that, take https://github.com/bytedance/deer-flowthe better argument is: you pay to vibe code and you'll pay again in 6 months to vibe fix, etc.It can, just have to include transcripts as part of commits and that's it.Sure it can!Why not? I maintain markdown files explaining everything (this is committed). Also the Python code is typed and has detailed numpydoc docstrings.
Seems like a skill issue. You could have had it create documentation along the way. The idea that prompts can't be versioned or iterated is patently false. Anything in the repo can be versioned.
hrm, there's tons of tools to do that, take https://github.com/bytedance/deer-flowthe better argument is: you pay to vibe code and you'll pay again in 6 months to vibe fix, etc.
Why not? I maintain markdown files explaining everything (this is committed). Also the Python code is typed and has detailed numpydoc docstrings.
Seems like a skill issue. You could have had it create documentation along the way. The idea that prompts can't be versioned or iterated is patently false. Anything in the repo can be versioned.
hrm, there's tons of tools to do that, take https://github.com/bytedance/deer-flow
the better argument is: you pay to vibe code and you'll pay again in 6 months to vibe fix, etc.
It can, just have to include transcripts as part of commits and that's it.
Sure it can!
Why not? I maintain markdown files explaining everything (this is committed). Also the Python code is typed and has detailed numpydoc docstrings.