ammar_az

I think this would a greatoption. Projects can start with two repos; one for code and one for docs. Then it would possible for code repo to add the docs one as submodule at anytime.

Actually I would suggest that to one of the projects that I'm currently involved in

It's a great thing if those changes live in their own repo and not mixed with changes to the code itself. Actually Jira has been doing that for a while now by offering the history view with a timeline for each change, also GitHub shows edit version for files as well.

The main role for projects management is handle the chaotic way of humans communication across different organization without developer being involved in that messy cycle. But having everything in the same repo will remove this decoupling and will let developers get involved in that chaos as it's part of the repo history.

Sure, it would be better if you get the right tools for it and teach people how to use it. At the end Google was able to get all of their source code in one mono git repository and it worked for them but they invest really heavily in their unique tooling.

However, I still think it would be much simpler to extend the tooling for current project management platform to give AI agents the text-based user interface that they needed. This would be much simpler task than developing the tooling for huge repo to include all the chaos of humans communications alongside the code itself.

The approach of having everything next to the code seems good in theory but it's just a nightmare in practice for big projects.

Imagine your git history filled with commits from project managers where every little change in requirements and docs has its own commit. We've tried that and ended up having to rebase our branches multiple times a day while we lost the overview of code changes completely.

The main issue that code can live in multiple branches while development but you can't apply that to docs and requirements where you need to have one centralized source of truth for everyone.

I think we will start to see more adaptation from collaboration tools to provide/accept the info in text format making it suitable for agents as a working solution. Meanwhile, I've seen that having two repos (One for Code and one for docs) is the best solution for the current tools available

I like to have my freedom in choosing what software I want to make/use, without anyone dictating what is better for me.

You like GUIs and want to build/use ones that works in MacOS, that's perfect go ahead and build as much GUIs as you want. However, this wouldn't work for me as I know how bad developing native cross-platform GUI applications is.

Posts like this are actually showing his expertise level with Zig rather than a comparison between Zig and Rust