*note: this post is a bit messy din't like the end result maybe update it lather or remake.
We debated the A.I. in previous "chapters", or posts, so now we can see that applying in some way.
The dependency's can be lather altered and moved around width a program, the concept is still very rudimentary, but can lather add more stuff like : the AI structure. Maybe a AI manager that will handle file manager and variable manager at another lever for us to minimizing errors.
We could handle the dependency that our programming structure have with, for example: we need to remove JPG dependency for our program.
The program should or will allow to add and remove dependency snippets, like grab and drop tool.
Can you remember where all those dependency's are? Probably not, even if you do you still have to search all files by hand inside which is a tedious task to do.
Lather on if we need to add or remove stuff, it can be done with a couple of clicks and not search inside files, or remember where stuff is. Which withdraw any possible help that a person can get in to a project, because not all people are developers of the code.
That is separate in to 2 ways if we can say that. People that are familiar with the internal code and can "move around" and others that have no knowledge of the internal and just want to extend some kind of functionality.
Well to extend they need to know how the internal is working in order to know the dependency's. In this case we have to 2 ways of doing that one with the external program, and another inside the code. In a way the 2 are inter depended of one another. If that doses not happen inside the code can't be lather automated in the program, because it have no knowledge of that. It need some kind of "giant" AI memory structure just to do that.
In another way if is structured internally can be managed out side, at least in a easy way.
"this stuff remove redundancy and errors from the code and allow automation in creation templates and game projects "
