I've been writing some posts under the rubric of "geoprocessing for humans". These are generally about keeping software simple, predictable, symmetrical, safe, readable, and well-documented. And simple. Most of all: simple.
- 1124. Geoprocessing for humans: close() and with
- 1122. Geoprocessing for humans: pygp
- 1121. Geoprocessing for humans: date and time
- 1119. Geoprocessing for humans: a pip requirements file
A couple of my recent posts are a little different, being about functional programming, partial functions, processing entire files of records without using any for loops, etc – stuff that a GIS programmer/analyst might not recognize as scripting or as even practical for all I know. I think I'll categorize these as "geoprocessing for hipsters". I don't usually begin coding in this way, but often arrive here after a few iterations.
- 1132. Mapping and Reducing
- 1128. Geoprocessing for hipsters: translating features
- 1126. More learning from Haskell
- 1125. Fiona, pyproj, Shapely in a functional style
If you find these rubrics fun and/or pedagogical, jump on in.