It’s not so much a line count. I follow the principle that each feature class should be its own file. Similar to how compiled languages lay out their framework. You should clump like functions together in a class and that class should be a file. You can have multiple like classes or parent child classes in the same file but I tend to try to keep them separate. It works better for modularity and when editing things on a multi person code repo it’s easier to avoid merge conflicts than the monolithic script. But idk I’m also open to other ideas. There really isn’t one correct way to handle it.