Should I write small CGI scripts or a big, monolithic script?

Writing a single CGI program is indeed better (slightly easier to reuse shared code) if you're not writing the dispatch code yourself If you commit to go this way, use a framework CGI-Application s concept of runmodes is basically the formalised concept of what your friend suggested, so this is a good choice for an advancing path Once you outgrow this system's limitations, have a look at Catalyst.

Writing a single CGI program is indeed better (slightly easier to reuse shared code) if you're not writing the dispatch code yourself. If you commit to go this way, use a framework. CGI-Application's concept of runmodes is basically the formalised concept of what your friend suggested, so this is a good choice for an advancing path.

Once you outgrow this system's limitations, have a look at Catalyst.

I tend to write separate scripts that share their commonality through libraries. If you're doing small things that simply show information, I think it's a waste of your time to learn a big framework. However, if you are going to start interacting with your scripts, running queries, and so on, a framework might be attractive and worth the effort.

Look at the scripts you have now and see how much is similar in each. If you are doing the same infrastructure coding in all of them, you might benefit from moving them into a single script. If they don't really look the same or do the same thing, you're probably not going to get that much benefit in the extra work.

I cant really gove you an answer,but what I can give you is a way to a solution, that is you have to find the anglde that you relate to or peaks your interest. A good paper is one that people get drawn into because it reaches them ln some way.As for me WW11 to me, I think of the holocaust and the effect it had on the survivors, their families and those who stood by and did nothing until it was too late.