You should point out that refusing to publish code is like being intentionally hazy about your experimental protocol.
When I started, code was jealously guarded as a "secret weapon" in the global competition for publishable results. Then the MILC group (http://physics.indiana.edu/~sg/milc.html) started releasing both their data and their code. The result was that they were widely cited and gained much respect in the scientific community, becoming a de facto standard, and facilitated research at institutions without the resources necessary for such computational preliminaries.
I'm pleased to say that this approach has become more the norm in this field at least, encouraged by SciDAC ( http://www.scidac.gov/) for example, with raw data (e.g. http://qcd.nersc.gov/, http://www.gridpp.ac.uk/qcdgrid/) and code (e.g. http://usqcd.jlab.org/usqcd-docs/chroma/, http://fermiqcd.net) being routinely made available.
The result is more science all round, which can only be a good thing. The "scooping" thing we all worried about turns out not be such an issue after all.
I am a proponent of open notebook science, and strongly believe that the benefits outweigh the negatives. Besides the feel-good arguments that this advances science and reproducibility, I'll point out a selfish motivation for releasing code: It makes it more likely that other researchers actually try your methodology and cite you.
I used to get mired down in trying to do formal releases. Now, I realized that releases are a hindrance, and by default all my research code lives in a github repo from day one:
http://github.com/turian
For example, here is the page I published on my word representation research, with links to my github code: http://metaoptimize.com/projects/wordreprs/