> Very little of what is actually needed to reproduce an experiment goes into academic papers.
This is also an issue where investigators apply custom software to complex systems. Getting source code can be nontrivial, and documentation is often inadequate. And there may be bugs that were avoided rather than patched.
>The problem with these lab books is that they're often the personal property of the scientists and, as such, almost a sort of diary
Further complicating things, individual researchers don't actually own the books. Often, an institution or the lab owns the rights to the book. This can make individuals who are otherwise keen on "open science" hesitant to place copies of this information in a publicly accessible place.
See page 4 of this manual from the NIH (National Institutes of Health) about the ownership of notebooks.
https://www.training.nih.gov/assets/Lab_Notebook_508_%28new%...
Everything on that page is stuff you're going to find in a grad student's lab books, which are their property. This document is basically a primer for people transitioning into paid research where the lab-books become lab property. A huge proportion of research, especially in less commercializable areas of fundamental science research, is done by students (because they're cheap). This means the kind of lab-book described in your link is probably less common that you might expect!
That kind of book sounds very useful for programmers. Any good tutorials on how to use one?
I'd imagine you can find guides on university websites. e.g. Search for physics, chemistry, etc. lab book format guides, etc.. These tend to be pretty formulaic and oriented towards ease of marking. However, they do establish habits that persist when experiments become life-consuming affairs rather than something that start and finish in a three hour period.
The problem with these lab books is that they're often the personal property of the scientists and, as such, almost a sort of diary. They're written with yourself as the intended audience and can sometimes be impenetrable for anyone else. If you're working in a commercial lab, as opposed to research in academia, these books might be considered the property of your employer. In this situation you might try to make them more friendly to other human beings, but that often isn't a priority.
Putting things into a digital form would, in general, take a lot longer. Even with good proficiency in LaTeX, complex equations are quicker to just write on paper. Hand-drawn diagrams are also very common in lab books, and the software/hardware to draw easily in a digital form is not yet ubiquitous. Finally, digital storage occasionally dies. A lab book is a precious possession whose loss can cause months or years of difficulty. Physical hard-copy is easier to store long-term. Some people have undergraduate lab books from half a century ago sitting on their office bookshelves.
There is nothing that is technologically insurmountable to moving to a digital lab book format. Microsoft's surface tablets make digital drawing pretty painless. Cloud storage could be maintained long-term. Etc. The benefits of digital lab books could be considerable. They'd be easier to search and distribute. You could include copies in a digital appendix to an experiment (currently, most journals discourage large attachments because they don't like to pay for storage). To my knowledge, nobody has actually put everything that's needed together into a single cohesive program. You'd want a note-taking program with full LaTeX and freehand drawing support. You'd need to be able to paste in tables, graphs, and data files easily. It would need to have a long-term archiving solution and a really good interface. It would need to be as fast or faster than writing on paper for pretty much everything. It would also probably need to be open source, as scientists would probably not trust proprietary software that might make their notes difficult to access at some point in the future. Finally, the hardware to run it on would need to be ubiquitous.