There have been pushes to publish more code in recent years. Most journal article formats at least allow for a "supplemental material" section like here: https:

There have been pushes to publish more code in recent years. Most journal article formats at least allow for a "supplemental material" section like here: https://journals.aps.org/prc/authors https://journals.aps.org/prc/authors Publishing code in a journal article in analogous to publishing key equations. Equations are just functions themselves after all. However, articles have to be succinct, and journals still exist in a hybrid physical/digital space. It isn't very useful to physically ink thousands of lines of code onto a page, especially if it represents a vastly different level of technical detail than the rest of the paper. In practice, people who write comprehensive software typically make it available through github or similar, and put a reference in the article. If not that, people will send you their code if you contact them. If they're stingy you may not get source, though. I don't know of any funding agency requirements that code source be made available, though I think that might be a good thing to try. I think the biggest difficulty is with medium-sized pieces of code. Small enough that the bookkeeping/maintenance needed to make it available gets skipped, but large enough that it isn't possible to provide details in the article.