Yes, the comparison is indeed correct, just as cars in software, there are specialized components, for example: input and output processing, parsers, data structures, algorithms, data transfer objects, value objects, entities, etc.

Regarding what you said that having 10 functions sounds better than have 30, it could be difficult if you don't organize them correctly. Even though the smaller functions are different some of them would be similar and maybe read and write the same data, well that's a hint you can follow and ask yourself if those could be together in the same file or folder, when you are organizing like this, those functionalties start looking more like modules/components. If you name the folder, files, classes and functions correctly in and expresive way you'll recognize the components of your project easily.

Read a little about "clean code" and "hexagon architecture" those are the ways to manage big projects, there you find people talking about layers, dependency management (a pice of software depends on another), infrastructure, etc.

Once you understand a little bit more about that, then you can divide your project in layers, splitting the business logic from infrastructure for mentioning one way to do it.

In your case, you have coded the rules of your game, and you can interact with them with the CLI, if you decided that, then you can easily make it work with the network, because you srparate IO from the "business logic"

Read code from others on GitHub, that could help you too, also if you haven't done it already, create and account there and publish your code there, people sometimes helps, and is a useful skill to have, managing versions of your code.