I went to a talk at SoCal Linux Expo called Build a Better Loop: A Guide to Platform Engineering (sorry, I am away from home and can't get you a link to the talk yet, but eventually the livestream will be edited and this talk will be available as a single youtube video)
One of the things the speaker, Arthur Freyman, suggested you do today is audit your legibility so AI agents can tell who owns and depends a service based on its name. In this article, you are suggesting something very similar, but the upshot is you are doing this as well! Of course, it makes it easy for both AI agents AND humans to figure out this information with a glance.
I went to a talk at SoCal Linux Expo called Build a Better Loop: A Guide to Platform Engineering (sorry, I am away from home and can't get you a link to the talk yet, but eventually the livestream will be edited and this talk will be available as a single youtube video)
One of the things the speaker, Arthur Freyman, suggested you do today is audit your legibility so AI agents can tell who owns and depends a service based on its name. In this article, you are suggesting something very similar, but the upshot is you are doing this as well! Of course, it makes it easy for both AI agents AND humans to figure out this information with a glance.
This kind of structure is very AI-friendly since you can make changes only in part of the project/domain and not interfere with others.
Maybe this can give you some other view: I find this structure rather basics for a large app https://www.linkedin.com/pulse/layer-pattern-vs-module-folder-structure-context-ai-machiraju-rdmec
Isn't the general idea the same? I mean, it's again about how you organize your folders or am I missing something?
yeah but like you only have the domain of the application, without folder for things like infra
Nice! Thanks for sharing!