Not all of my colleagues know how to code, but they do know how to interpret results, plots and so on (I'm in science, by the way). In my case, I am not interested in version controlling the notebook; it's just for quick prototyping and discussing ideas. I only need to version control the Python file. Also, colleagues who don't code (or dislike coding) can easily modify parameters in the notebook and obtain different results immediately with no additional effort.
Jupiter is excellent at what it is designed for. For example, my usual workflow is as follows: when I develop a tool or model, I do so in a plain Python file. I then import the file from the notebook to create figures, demonstrations, documentation and so on, resulting in an immediate document that my colleagues and I can easily use for discussion. It's as simple and effective as that. It is also a great tool for teaching coding to beginners. Of course, notebooks are not designed for code development. Also, nowadays, if you want to, you can open notebooks in dedicated apps.
Interestingly, Earth scientists have long understood that plate tectonics is highly unlikely to exist on a rocky planet without water (to put it simply, water is needed to deform the Earth's upper mantle), given all that this entails. If this hypothesis is true, plate tectonics as such should be post-collision.
This is only partly true. Because low-temperature extraction is much less efficient, it requires a much longer immersion/exposure time than hot extraction at ambient or slightly higher pressure. One of the effects of this type of cold extraction is the oxidation of the coffee, which is much greater with this method, giving the coffee an oxidised taste which, although not bad in itself (nothing is set in stone about personal taste), is not to everyone's liking. For my taste, I prefer to make it hot (with a higher coffee/water ratio than usual) and cool it down by diluting it with water or ice.