@mtb-za I have just re-read your Bentley 2 chapter.
Apart from perhaps two typos that I mentally registered but ignored, I have no recommendations for changes, just comments. But it is ready to go!
This is a nice chapter. Very readable.
I think it'll make a useful read both for someone that is coding for colleagues that have no programming experience, and for those colleagues (they too can be educated about some of these dilemmas).
I say this as someone that paid an undergrad computer science student (with a few weekly pizzas and some Italian tutoring) to write Perl scripts (circa 2002, when I knew very little CS, and could not even, yet, write Matlab scripts) to do just these kind of works, but on a scale of tens of thousands of proprietary files from 3C seismometers, and had to be educated to some extent, at least to be able to explain, in the appendix of my Master's thesis, what was going on.
@mtb-za I have just re-read your Bentley 2 chapter.
Apart from perhaps two typos that I mentally registered but ignored, I have no recommendations for changes, just comments. But it is ready to go!
This is a nice chapter. Very readable.
I think it'll make a useful read both for someone that is coding for colleagues that have no programming experience, and for those colleagues (they too can be educated about some of these dilemmas).
I say this as someone that paid an undergrad computer science student (with a few weekly pizzas and some Italian tutoring) to write Perl scripts (circa 2002, when I knew very little CS, and could not even, yet, write Matlab scripts) to do just these kind of works, but on a scale of tens of thousands of proprietary files from 3C seismometers, and had to be educated to some extent, at least to be able to explain, in the appendix of my Master's thesis, what was going on.