Sean Gillies (Posts about ironic)https://sgillies.net/tags/ironic.atom2023-12-31T01:26:23ZSean GilliesNikolaOngoing blog serieshttps://sgillies.net/2012/02/24/ongoing-blog-series.html2012-02-24T00:00:00-07:002012-02-24T00:00:00-07:00Sean Gillies<p>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.</p>
<ul class="simple">
<li><p><a class="reference external" href="http://sgillies.net/blog/1124/geoprocessing-for-humans-close-and-with/">1124. Geoprocessing for humans: close() and with</a></p></li>
<li><p><a class="reference external" href="http://sgillies.net/blog/1122/geoprocessing-for-humans-pygp/">1122. Geoprocessing for humans: pygp</a></p></li>
<li><p><a class="reference external" href="http://sgillies.net/blog/1121/geoprocessing-for-humans-date-and-time/">1121. Geoprocessing for humans: date and time</a></p></li>
<li><p><a class="reference external" href="http://sgillies.net/blog/1119/geoprocessing-for-humans-a-pip-requirements-file/">1119. Geoprocessing for humans: a pip requirements file</a></p></li>
</ul>
<p>A couple of my recent posts are a little different, being about functional
programming, partial functions, processing entire files of records without using
any <code class="docutils literal">for</code> 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.</p>
<ul class="simple">
<li><p><a class="reference external" href="http://sgillies.net/blog/1132/mapping-and-reducing">1132. Mapping and Reducing</a></p></li>
<li><p><a class="reference external" href="http://sgillies.net/blog/1128/geoprocessing-for-hipsters-translating-features">1128. Geoprocessing for hipsters: translating features</a></p></li>
<li><p><a class="reference external" href="http://sgillies.net/blog/1126/more-learning-from-haskell">1126. More learning from Haskell</a></p></li>
<li><p><a class="reference external" href="http://sgillies.net/blog/1125/fiona-pyproj-shapely-in-a-functional-style">1125. Fiona, pyproj, Shapely in a functional style</a></p></li>
</ul>
<p>If you find these rubrics fun and/or pedagogical, jump on in.</p>In which I try to help more and complain lesshttps://sgillies.net/2010/12/22/in-which-i-try-to-help-more-and-complain-less.html2010-12-22T00:00:00-07:002010-12-22T00:00:00-07:00Sean Gillies<p><strong>Update</strong> (2011-01-12): Better: <a class="reference external" href="http://sgillies.net/blog/1065/thats-more-like-it">http://sgillies.net/blog/1065/thats-more-like-it</a></p>
<p>A reader suggested to me in comments that I should approach the words on the
FOSS4G 2011 site (which I quoted <a class="reference external" href="http://sgillies.net/blog/1059/copywriting-run-amuck">previously</a>) from a different angle and try to
appreciate that they're aimed at folks outside the FOSS4G community. Speaking
to them using their own language including, apparently, their own unflattering
stereotypes of open source users in an anything goes effort to lure them in to
the event. I suppose this makes some twisted sense if you ignore an
eventuality: that this corporate audience will at some point discover
themselves fully surrounded by these very same wild-eyed open source hippy
freetard philosophers. But nevermind that for now, I'm fully onboard with the
FOSS4G rhetoric and have some other stereotypes that the marketers are free to
use or repurpose if the original</p>
<blockquote>
<p>Many early adopters of FOSS solutions chose them based on
"philosophical" reasons, but ...</p>
</blockquote>
<p>starts to wear thin. How about this one, which uses unnecessary quotes to
maintain the right style?</p>
<blockquote>
<p>Many early adopters of FOSS solutions were into GIS as a "fun" hobby, but ...</p>
</blockquote>
<p>That will have strong appeal for certified professionals.</p>
<blockquote>
<p>Many early adopters of FOSS solutions felt "everything" should be free, but
...</p>
</blockquote>
<p>The conference is coming back to the USA, and nothing is more American than
using Communists as bogeymen.</p>
<blockquote>
<p>Many early adopters of FOSS ranted about the "difference" between freedom and
free beer, but ...</p>
</blockquote>
<p>Always with the damn philosophizing, those freetards.</p>
<blockquote>
<p>Many early adopters of FOSS were from "academic" backgrounds, but ...</p>
</blockquote>
<p>I almost forgot the Ivory Tower! Nobody is less pragmatic than an academic researcher, right? Hope this helps, and
Merry Christmas.</p>Can't happen herehttps://sgillies.net/2009/11/05/cant-happen-here.html2009-11-05T00:00:00-07:002009-11-05T00:00:00-07:00Sean Gillies<p>Says Paul Ramsey in <a class="reference external" href="http://blogs.weogeo.com/pbissett/2009/10/14/goog-borg-and-i-mean-that-in-the-nicest-way/comment-page-1/#comment-190">comments</a> on Paul Bissett's great post about disruption of the data and navigation business:</p>
<blockquote>
<p>Right, a black hole isn’t “evil”, but that doesn’t change the fact that it massively distorts the shape of space-time everywhere it goes, which can be a bummer for any object in its immediate neighbourhood.</p>
</blockquote>
<p>Thank the gods that Digital Classicism isn't GIS. It can't happen here.</p>