I have always referred to the things I write to be run by a machine as 'code'. As in "This FORTRAN code calculates the centroid of an object", or "That Perl code monitors these logs and sends alerts".

I know folks who really try hard to make a distinction between 'compiled' and 'interpreted', the former being "code" and the latter "script"; but they are having a tough go explaining to me why Java is code and preprocessed C isn't script.

Personally, I have always thought the distinction was merely semantic. "Code versus Script" serves the niche in Geekdom that "How 'bout them Dogs" serves for Football fanatics. It's a good starting place for a conversation in the Local after work, and a reason for ordering another round of beer; but it's not really meaningful in the larger scheme of things.