Geoscientists and Geo-engineers Need to Code

Michael Pyrcz, P.Eng., Ph.D. 

I could write a lengthy essay on my experience, feelings about this topic or I could just give you a very concise list of the reasons.  I had originally written and posted the one below on twitter (@GeostatsGuy) in Q3, 2017 as a response to Prof. Brian Romans, a good friend and well known stratigrapher at Virginia Tech.  Go here to check out Prof. Roman's work:

I have assumed that engineers need no convincing.  My personal experience as an engineering undergraduate student included: one dedicated coding class and 2-3 classes that required extensive coding on the regular assignments, and then a computational geostatistics Ph.D. with Prof. Clayton Deutsch with a lot of Fortran, and subsequently learning the basics of C++ in a couple of weeks so I could code for Chevron during an internship.  Subsequently, I have realized, to my surprise that not all engineers enjoy coding.  To those this is extended.  Also, I want to acknowledge that not all geologists need convencing.  Consider the computational geologists that code for their numerical experiments (e.g. Profs. Chris Paola, David Mohrig and Kyle Straub's experimental stratigraphy groups), and those brave observational, outcrop-oriented that recognize the benefit of coding for automation and quantification (more on quantification later).  I hope this is helpful.  I'm always happy to discuss.