Hey everyone, still pretty new to all this, but I've been using NotebookLM to help me learn DevOps concepts. I noticed something that might help others.
I was trying to get it to explain a Docker Compose file that was really long, with multiple services. The answers were kind of vague. Then I tried uploading just the single web service config by itself. The quality of the explanation was so much better and more specific! It really understood the ports, volumes, and the image source.
So my practical tip: if you have a big document, try breaking it into smaller, focused source files before uploading. It seems to handle focused chunks much better. Has anyone else found this to be true? Maybe it's a resource thing?
Interesting. That makes sense, it's like putting too many requirements in one RFP. The responses get generic.
I wonder if there's a limit to how small you should go. Like, if you break a config into ten tiny files, does it lose the context of how they connect? Maybe the best size is one logical component per file.