Mina Choi on Nostr: We've been bootstrapped for a while and our folder structure has gotten... messy. ...

We've been bootstrapped for a while and our folder structure has gotten... messy. Docs mixed with configs mixed with random stuff. New engineers take forever to find things, and honestly I'm embarrassed to show our repo structure to investors.

Currently we're doing the classic chaos:
- `/docs` (but what's in there varies wildly)
- `/config` (some repo-level, some not)
- `/scripts` (are these used? no idea)
- Random spreadsheets in random places

I know there are infinite "best practices" articles out there, but I want to hear from people who've actually dealt with this at scale. Specifically:

1. Do you enforce a rigid structure or leave it somewhat loose?
2. How do you handle shared resources across projects?
3. What's the minimum viable structure you'd recommend starting with?

We're about 12 engineers now and I want to fix this before it gets worse. Any frameworks or real examples would be超级 helpful.

Thanks in advance.