Original Summary

We have a few people under our CTO who do a lot of the basic work via vibe code, and the CTO reviews and does the back-end heavy lifting. We have multiple projects going with lots of code borrowed from different places, and it’s getting very confusing about where everything fits. For example, the other day I realized I had wasted a lot of time accidentally re-building a feature we had in another project, but then someone else hadn’t built/merged in the correct repo, and some things just got really tangled. For reference, we do bespoke wealth management infrastructure. We’ve been thinking about better ways to map our systems/features in a better way that Claude understands so we don’t have to keep going back and forth with Linear and double checking each other. What’s a best practice here? Any mapping/defined rules that we can plug and play for our team when they’re using Claude/codex? Or am I being naive about how far we can get with vibe coding?   submitted by   /u/ExpensiveToes4729 [link]   [comments]

  • 情报分类：技术学习与提效
  • 分类依据：内容涉及技术、AI、软件工具或工程实践
  • 信息来源：Reddit · SaaS
  • 发布时间：2026/10/21 02:43:47