Depends a bit on the area. You can machine-code results if the field is extremely static in its conceptual and epistemic framework, so it's just a matter of slo

Depends a bit on the area. You can machine-code results if the field is extremely static in its conceptual and epistemic framework, so it's just a matter of slotting new things in place. Some "industrial-style" science does work like that. But large areas don't. Most of the articles I read have the majority of the actual research going on in the text, not in whatever the "results" might nominally be. For example, a programming language paper might prove a few theorems about type-soundness, but it's rare that a new type-soundness theorem is really want you want out of the paper; that's just supporting apparatus. What's more interesting is the design discussion, motivation for why this feature was introduced and how it relates to previous features, explanation of how it was implemented, discussion of variants and future work, etc.