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.
A couple of my recent posts are a little different, being about functional
programming, partial functions, processing entire files of records without using
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.
If you find these rubrics fun and/or pedagogical, jump on in.