This seems to imply that the projects you have in mind are likely to involve inter-process communication (IPC), child processes and the like. If so, it might move things forward more quickly to describe what you have in mind to implement, and what parts of the implementation are still mysterious to you.

Any notion at all that you can come up with about how to split a project into distinct processes is good enough for a start -- try something out, maybe even try a couple variations, and if you get into trouble with that, share the details of the specific problem. General knowledge in the absence of particular usage is of questionable value.

Also, I see you've been reading a lot of books. Have you been reading manual pages too? If not, you need to do that. For the question at hand, if you haven't read perlipc, then that is the next thing you should do. You probably won't understand all of it (I suspect there are parts I don't quite understand yet), but you should be able to locate sections that will be relevant to what you want to do next, and you should be able to make some sense of those sections -- at least, enough to try a few things out.

Then again, if the projects you have in mind don't really depend crucially on process management and IPC, then why put off moving ahead with these projects? Let the IPC know-how come to you if/when the need arises. Just because you lack this know-how at the moment doesn't mean you can't do anything.