<?xml version="1.0" encoding="utf-8"?>
<?xml-stylesheet type="text/xsl" href="../assets/xml/rss.xsl" media="all"?><rss version="2.0" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Sean Gillies (Posts about blog)</title><link>https://sgillies.net/</link><description></description><atom:link href="https://sgillies.net/tags/blog.xml" rel="self" type="application/rss+xml"></atom:link><language>en</language><lastBuildDate>Sun, 31 Dec 2023 01:26:21 GMT</lastBuildDate><generator>Nikola (getnikola.com)</generator><docs>http://blogs.law.harvard.edu/tech/rss</docs><item><title>New cert for the site</title><link>https://sgillies.net/2017/11/28/new-cert-for-the-site.html</link><dc:creator>Sean Gillies</dc:creator><description>&lt;p&gt;Earlier today my old certificate from gandi.net expired while
my new one was pending, leaving my blog twisting in the wind. I had
such a positive experience &lt;a class="reference external" href="https://sgillies.net/2017/11/11/lets-encrypt-and-certbot.html"&gt;two weeks ago&lt;/a&gt; with
certbot on my local trails web app, that I did the same for
my main site this evening. I hope you weren't inconvenienced by a couple hours
of security warnings.&lt;/p&gt;</description><category>blog</category><category>certbot</category><category>https</category><category>let's encrypt</category><category>life</category><category>ssl</category><guid>https://sgillies.net/2017/11/28/new-cert-for-the-site.html</guid><pubDate>Wed, 29 Nov 2017 07:00:51 GMT</pubDate></item><item><title>Bringing Blogging Back</title><link>https://sgillies.net/2017/10/14/bringing-blogging-back.html</link><dc:creator>Sean Gillies</dc:creator><description>&lt;p&gt;I'm unhappy with Twitter, the platform, and its featured user, the
Asshole-in-Chief of the U.S.A. Without a better idea, I'm bringing blogging
back. Bookmark &lt;a class="reference external" href="https://sgillies.net/tags/life.html"&gt;https://sgillies.net/tags/life.html&lt;/a&gt; or
&lt;a class="reference external" href="https://sgillies.net/tags/work.html"&gt;https://sgillies.net/tags/work.html&lt;/a&gt;, or both. Drop them into Feedly or
whatever. This is where you can find out what I'm up to and what I'm thinking
about.&lt;/p&gt;</description><category>blog</category><category>life</category><category>work</category><guid>https://sgillies.net/2017/10/14/bringing-blogging-back.html</guid><pubDate>Sat, 14 Oct 2017 23:59:54 GMT</pubDate></item><item><title>Blog Makeover</title><link>https://sgillies.net/2016/10/06/blog-makeover.html</link><dc:creator>Sean Gillies</dc:creator><description>&lt;p&gt;The feature I need  most in a static site generator right now is
incremental builds. Regenerating the hundreds of existing posts on my site
has become a barrier to posting often.
I'm trying &lt;a class="reference external" href="https://getnikola.com/"&gt;Nikola&lt;/a&gt; and am satisfied so far.
With each new post there are still a number of files to be regenerated
– the index page and feed, pages and feeds for tags I've used – but the
write, preview, publish cycle feels much faster.&lt;/p&gt;
&lt;p&gt;Syndication feeds for the tags I use is a feature I
gave up in 2013 when I quit blogging on Zope, but they're back thanks to
Nikola. See &lt;a class="reference external" href="https://sgillies.net/tags/rasterio.html"&gt;https://sgillies.net/tags/rasterio.html&lt;/a&gt; and
&lt;a class="reference external" href="https://sgillies.net/tags/rasterio.atom"&gt;https://sgillies.net/tags/rasterio.atom&lt;/a&gt; for example.&lt;/p&gt;
&lt;p&gt;I'm using "work" and "life" tags to make it easier to subscribe to posts
that are mainly about programming and spatial data processing or posts
that are mainly about food, running, and being a temporary resident of France.
This doesn't mean that I'm making my work feed a safe space for people who
don't want to hear about workplace diversity, climate change, and politics
or that there won't be any posts about maps and computing in my lifestyle feed.&lt;/p&gt;
&lt;p&gt;Thanks for reading my blog. I hope the changes work for you, too.&lt;/p&gt;</description><category>blog</category><category>life</category><category>nikola</category><guid>https://sgillies.net/2016/10/06/blog-makeover.html</guid><pubDate>Thu, 06 Oct 2016 20:14:46 GMT</pubDate></item><item><title>Downgrading my blog</title><link>https://sgillies.net/2013/10/07/downgrading-my-blog.html</link><dc:creator>Sean Gillies</dc:creator><description>&lt;p&gt;Welcome to my new blog. It's made with &lt;a class="reference external" href="http://tinkerer.me"&gt;Tinkerer&lt;/a&gt;.
I'm calling it a downgrade because there's no more database, no more comments,
no more Python objects published for every request. It's just rsync and static
HTML generated by Tinkerer and Sphinx from ReStructured Text docs I type into
Vim.  There are moving parts in this new blog, but they are all on my laptop.
None of them are deployed to a web server.&lt;/p&gt;
&lt;p&gt;My old posts were all written using ReST, so migrating is going to be easy
peasy. Until I get around to it, old posts will be at
&lt;a class="reference external" href="http://sgillies.net/olden-days-blog/"&gt;http://sgillies.net/olden-days-blog/&lt;/a&gt; and I'll make sure the old URLs redirect.&lt;/p&gt;</description><category>blog</category><category>life</category><category>restructuredtext</category><category>sphinx</category><category>tinkerer</category><guid>https://sgillies.net/2013/10/07/downgrading-my-blog.html</guid><pubDate>Mon, 07 Oct 2013 06:00:00 GMT</pubDate></item><item><title>Ongoing blog series</title><link>https://sgillies.net/2012/02/24/ongoing-blog-series.html</link><dc:creator>Sean Gillies</dc:creator><description>&lt;p&gt;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.&lt;/p&gt;
&lt;ul class="simple"&gt;
&lt;li&gt;&lt;p&gt;&lt;a class="reference external" href="http://sgillies.net/blog/1124/geoprocessing-for-humans-close-and-with/"&gt;1124. Geoprocessing for humans: close() and with&lt;/a&gt;&lt;/p&gt;&lt;/li&gt;
&lt;li&gt;&lt;p&gt;&lt;a class="reference external" href="http://sgillies.net/blog/1122/geoprocessing-for-humans-pygp/"&gt;1122. Geoprocessing for humans: pygp&lt;/a&gt;&lt;/p&gt;&lt;/li&gt;
&lt;li&gt;&lt;p&gt;&lt;a class="reference external" href="http://sgillies.net/blog/1121/geoprocessing-for-humans-date-and-time/"&gt;1121. Geoprocessing for humans: date and time&lt;/a&gt;&lt;/p&gt;&lt;/li&gt;
&lt;li&gt;&lt;p&gt;&lt;a class="reference external" href="http://sgillies.net/blog/1119/geoprocessing-for-humans-a-pip-requirements-file/"&gt;1119. Geoprocessing for humans: a pip requirements file&lt;/a&gt;&lt;/p&gt;&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;A couple of my recent posts are a little different, being about functional
programming, partial functions, processing entire files of records without using
any &lt;code class="docutils literal"&gt;for&lt;/code&gt; 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.&lt;/p&gt;
&lt;ul class="simple"&gt;
&lt;li&gt;&lt;p&gt;&lt;a class="reference external" href="http://sgillies.net/blog/1132/mapping-and-reducing"&gt;1132. Mapping and Reducing&lt;/a&gt;&lt;/p&gt;&lt;/li&gt;
&lt;li&gt;&lt;p&gt;&lt;a class="reference external" href="http://sgillies.net/blog/1128/geoprocessing-for-hipsters-translating-features"&gt;1128. Geoprocessing for hipsters: translating features&lt;/a&gt;&lt;/p&gt;&lt;/li&gt;
&lt;li&gt;&lt;p&gt;&lt;a class="reference external" href="http://sgillies.net/blog/1126/more-learning-from-haskell"&gt;1126. More learning from Haskell&lt;/a&gt;&lt;/p&gt;&lt;/li&gt;
&lt;li&gt;&lt;p&gt;&lt;a class="reference external" href="http://sgillies.net/blog/1125/fiona-pyproj-shapely-in-a-functional-style"&gt;1125. Fiona, pyproj, Shapely in a functional style&lt;/a&gt;&lt;/p&gt;&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;If you find these rubrics fun and/or pedagogical, jump on in.&lt;/p&gt;</description><category>blog</category><category>ironic</category><category>programming</category><category>python</category><category>the lab</category><category>work</category><guid>https://sgillies.net/2012/02/24/ongoing-blog-series.html</guid><pubDate>Fri, 24 Feb 2012 07:00:00 GMT</pubDate></item><item><title>Station Identification</title><link>https://sgillies.net/2012/01/01/station-identification.html</link><dc:creator>Sean Gillies</dc:creator><description>&lt;p&gt;Since March 2005, this is the blog of &lt;a class="reference external" href="http://sgillies.net"&gt;Sean Gillies&lt;/a&gt;.&lt;/p&gt;
&lt;p&gt;These are my words only and not those of my employer, coworkers, family, or
friends. I have agendas, but no particular strategy. I write when I can about
whatever I find interesting, and it will be more of the same this year:
commercial free observations, thinking out loud, big blocks of code, and
lessons learned. I published 56 posts in 2012, up from 47 in 2011, and hope to
bump the quantity and quality up again in 2013. Comments are welcome,
a privilege of having a modest number of always thoughtful readers, but please
do read my &lt;a class="reference external" href="http://sgillies.net/blog/422/my-comment-policy/"&gt;comments policy&lt;/a&gt;.&lt;/p&gt;
&lt;p&gt;The idea to post a yearly station identification comes from John Scalzi's
&lt;a class="reference external" href="http://whatever.scalzi.com/2012/01/01/station-identification-whatever/"&gt;Whatever&lt;/a&gt;
blog.&lt;/p&gt;
&lt;p&gt;Peviously: &lt;a class="reference external" href="http://sgillies.net/blog/1109/station-identification/"&gt;2012&lt;/a&gt;.&lt;/p&gt;</description><category>blog</category><category>work</category><guid>https://sgillies.net/2012/01/01/station-identification.html</guid><pubDate>Sun, 01 Jan 2012 07:00:00 GMT</pubDate></item></channel></rss>