The Mess Nobody Warns You About When You Build With AI

I'm going to explain something to you guys because it's going to be a little hard to explain. When I tell it to organize, say, the top layer of the album, I didn't say it like that. I said organize the album. But what it does is organize the top layer of the album. It doesn't go into the individual album to see if there's an album inside an album. It loves creating albums. It loves creating documents and duplicates. And that causes a lot of problems when you're using these AI systems.

That is something that I'm trying to break right now and figure out the terminology to use so it stops doing that. A mess. It is a mess.

I may be recreating the wheel. I don't think a lot of people are doing this exactly the way I'm doing it. When I first started music, of course, I wasn't organizing things the way they should have been organized because I just been in this sprint of learning things. And before I put out the Spanish album, I want this organized. AM I INSANE went well. The Romanian one, still closer to going well. The Spanish one, I want it to be perfect. And in order for that to be perfect when I automate that system, I need all these layers to be in order.

So every step I make it take notes. I make it tell itself what it did wrong and what it needs to fix. This has been a nightmare of a process. This is not easy. Why am I doing this? Because everything I do is about being the human guiding the system. I don't want somebody else's blueprint. I want my own blueprint.

I'm building my own system. I'm making sure everything is original to me so anything ever comes back to me and they cannot say this is not mine. I have too much metadata. This is the future and this is going to be very important for people to do. It's going to be very important to keep up with your metadata. It is everything.

I'm going deeper. Every time I do something, it's going deeper to explain to it what I'm doing because it's going to find files and it's wondering, well, why did she put that label on it? I got to guide it.

So for instance, for a French file, I always have brackets. For French, I only know that I'm doing one language that starts with an F, that's French. So I put F for French and then F for female. F for French, M for male. F for French, D for Duet. Then if it's my number one song, then I put a one there. It's the first album. If it's the second song on the first album, that'll be FF1 number two because it's the second song on the album. So I have labels for everything.

With AI, you don't have to follow anybody else's rules. All that stuff about getting to this point where you need to do this way and this way for things to work, you don't have to do that. You can do things according to what you want. Again, everything I do is doing things original to me and how things work for me. We're outside of the system now. Forget the system. We're creating our own.

So when I get out there and you want to hire me to work for your business, you best believe everything I do for you will be original. It will be according to what you want and not a template and not an answer that everybody was told that it had to be. I'm not doing that anymore. I don't have to.

My ISRC codes are mine, and they are embedded inside my own masters, not only typed into a form. A form can be wrong. A file cannot argue with what is written inside it.

Everything I do is about being the human guiding the system. I do not want somebody else's blueprint. I want my own, and the metadata is what proves it is mine. With AI you do not have to follow anybody else's rules. We are outside of the system now.