<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Luc Perkins</title><link>https://lucperkins.dev/</link><description>Recent content on Luc Perkins</description><generator>Hugo</generator><language>en-us</language><managingEditor>lucperkins@gmail.com (Luc Perkins)</managingEditor><webMaster>lucperkins@gmail.com (Luc Perkins)</webMaster><lastBuildDate>Fri, 04 Nov 2022 00:00:00 +0000</lastBuildDate><atom:link href="https://lucperkins.dev/index.xml" rel="self" type="application/rss+xml"/><item><title>Developer experience and the membrane layer</title><link>https://lucperkins.dev/blog/membrane-layer/</link><pubDate>Fri, 04 Nov 2022 00:00:00 +0000</pubDate><author>lucperkins@gmail.com (Luc Perkins)</author><guid>https://lucperkins.dev/blog/membrane-layer/</guid><description>&lt;p&gt;I&amp;rsquo;ve done a whole lot of, err, stuff in software—plain old dev work, tech writing, DevRel, all and sundry &amp;ldquo;glue work&amp;rdquo;—but when pressed for a single designation for what I do I usually just say that I specialize in &lt;strong&gt;developer experience&lt;/strong&gt; (or &lt;strong&gt;DevEx&lt;/strong&gt; for short).
While I have an intuitive sense of what DevEx is, I&amp;rsquo;ve often struggled to explain it, not just to friends and family who don&amp;rsquo;t know much about technology but even to other industry insiders.
A while back, though, right in the middle of a job interview, I came up with an analogy that&amp;rsquo;s stuck with me and that I&amp;rsquo;ll probably use until the end of my days in the industry.&lt;/p&gt;</description></item><item><title>The easiest way (I've found) to create your own Nix channel</title><link>https://lucperkins.dev/blog/nix-channel/</link><pubDate>Mon, 10 Aug 2020 00:00:00 +0000</pubDate><author>lucperkins@gmail.com (Luc Perkins)</author><guid>https://lucperkins.dev/blog/nix-channel/</guid><description>&lt;p&gt;There are lots of ways of creating Nix channels, but in this post I&amp;rsquo;d like to highlight the fastest and easiest way I&amp;rsquo;ve found thus far: via &lt;strong&gt;GitHub archives&lt;/strong&gt;. I discovered this method when installing &lt;a href="https://github.com/rycee/home-manager"target="_blank"&gt;Home Manager&lt;sup&gt;&lt;i class="fas fa-external-link-alt"&gt;&lt;/i&gt;&lt;/sup&gt;&lt;/a&gt;. Nix channels are essentially tarballs that are available via an unchanging URL. Quite conveniently, GitHub has a built-in archive feature that automatically turns every branch in every GitHub repo into a tarball available at a URL with this structure:&lt;/p&gt;</description></item><item><title>From Homebrew to Home Manager</title><link>https://lucperkins.dev/blog/home-manager/</link><pubDate>Thu, 16 Jul 2020 00:00:00 +0000</pubDate><author>lucperkins@gmail.com (Luc Perkins)</author><guid>https://lucperkins.dev/blog/home-manager/</guid><description>&lt;p&gt;Don&amp;rsquo;t get me wrong: I have nothing against &lt;a href="https://brew.sh"target="_blank"&gt;Homebrew&lt;sup&gt;&lt;i class="fas fa-external-link-alt"&gt;&lt;/i&gt;&lt;/sup&gt;&lt;/a&gt;, the macOS package manager that most devs who run Apple laptops use on a near-daily basis. It&amp;rsquo;s served me admirably all these years and I&amp;rsquo;ve even written some Homebrew recipes.&lt;/p&gt;
&lt;p&gt;But I&amp;rsquo;ve become convinced that there&amp;rsquo;s a better way&amp;mdash;or at least a way that suits my needs better. I recently switched from Homebrew to &lt;a href="https://github.com/rycee/home-manager"target="_blank"&gt;Home Manager&lt;sup&gt;&lt;i class="fas fa-external-link-alt"&gt;&lt;/i&gt;&lt;/sup&gt;&lt;/a&gt;, the &lt;a href="https://nixos.org/nix"target="_blank"&gt;Nix&lt;sup&gt;&lt;i class="fas fa-external-link-alt"&gt;&lt;/i&gt;&lt;/sup&gt;&lt;/a&gt;-based user environment manager created by &lt;a href="https://github.com/rycee"target="_blank"&gt;Robert Helgesson&lt;sup&gt;&lt;i class="fas fa-external-link-alt"&gt;&lt;/i&gt;&lt;/sup&gt;&lt;/a&gt;, and I&amp;rsquo;ve been extremely pleased with the results so far. Home Manager has enabled me to establish a fully &lt;strong&gt;declarative approach&lt;/strong&gt; to managing my laptop environment, including my dotfiles.&lt;/p&gt;</description></item><item><title>Service mesh use cases</title><link>https://lucperkins.dev/blog/service-mesh-use-cases/</link><pubDate>Mon, 29 Jun 2020 00:00:00 +0000</pubDate><author>lucperkins@gmail.com (Luc Perkins)</author><guid>https://lucperkins.dev/blog/service-mesh-use-cases/</guid><description>&lt;p&gt;&lt;a href="https://en.wikipedia.org/wiki/Service_mesh"target="_blank"&gt;Service mesh&lt;sup&gt;&lt;i class="fas fa-external-link-alt"&gt;&lt;/i&gt;&lt;/sup&gt;&lt;/a&gt; is a blazing hot topic in software engineering right now and rightfully so. I think it&amp;rsquo;s extremely promising technology and I&amp;rsquo;d love to see it widely adopted (in cases where it truly makes sense). Yet it remains shrouded in mystery for many people and even those who &lt;em&gt;are&lt;/em&gt; familiar with it have trouble articulating what it&amp;rsquo;s good for and what it even is (like yours truly). In this post, I&amp;rsquo;m going to help rectify that by providing a simple &lt;strong&gt;list of use cases&lt;/strong&gt; for service meshes.&lt;/p&gt;</description></item><item><title>Recent database technology that should be on your radar (part 1)</title><link>https://lucperkins.dev/blog/new-db-tech-1/</link><pubDate>Mon, 15 Jun 2020 00:00:00 +0000</pubDate><author>lucperkins@gmail.com (Luc Perkins)</author><guid>https://lucperkins.dev/blog/new-db-tech-1/</guid><description>&lt;p&gt;I&amp;rsquo;m a &lt;strong&gt;huge&lt;/strong&gt; fan of databases, so much so that I&amp;rsquo;ve &lt;a href="https://7dbs.io"target="_blank"&gt;written a book&lt;sup&gt;&lt;i class="fas fa-external-link-alt"&gt;&lt;/i&gt;&lt;/sup&gt;&lt;/a&gt; on so-called &amp;ldquo;NoSQL&amp;rdquo; databases, I spent some of my most fruitful years in tech working on the highly influential distributed database &lt;a href="https://riak.com"target="_blank"&gt;Riak&lt;sup&gt;&lt;i class="fas fa-external-link-alt"&gt;&lt;/i&gt;&lt;/sup&gt;&lt;/a&gt;, and I even built a database called &lt;a href="https://purpledb.io/"target="_blank"&gt;Purple&lt;sup&gt;&lt;i class="fas fa-external-link-alt"&gt;&lt;/i&gt;&lt;/sup&gt;&lt;/a&gt; last year just for fun.&lt;/p&gt;
&lt;p&gt;Naturally, I&amp;rsquo;m always on the lookout for new and exciting developments in databases and DB-related tools when I scan (trash fires like) Twitter, Reddit, and HackerNews. In this post I&amp;rsquo;d like to talk about three recently minted database technologies that I find intriguing:&lt;/p&gt;</description></item><item><title>A new way forward for technical documentation? Part 1: the problematic status quo</title><link>https://lucperkins.dev/blog/docs-new-way-forward-1/</link><pubDate>Tue, 21 Jan 2020 00:00:00 +0000</pubDate><author>lucperkins@gmail.com (Luc Perkins)</author><guid>https://lucperkins.dev/blog/docs-new-way-forward-1/</guid><description>&lt;p&gt;I&amp;rsquo;ve contributed to many very large documentation projects in my day, including &lt;a href="https://riak.com"target="_blank"&gt;Riak&lt;sup&gt;&lt;i class="fas fa-external-link-alt"&gt;&lt;/i&gt;&lt;/sup&gt;&lt;/a&gt;, &lt;a href="https://kubernetes.io"target="_blank"&gt;Kubernetes&lt;sup&gt;&lt;i class="fas fa-external-link-alt"&gt;&lt;/i&gt;&lt;/sup&gt;&lt;/a&gt;, &lt;a href="https://prometheus.io"target="_blank"&gt;Prometheus&lt;sup&gt;&lt;i class="fas fa-external-link-alt"&gt;&lt;/i&gt;&lt;/sup&gt;&lt;/a&gt;, &lt;a href="https://pulsar.apache.org"target="_blank"&gt;Pulsar&lt;sup&gt;&lt;i class="fas fa-external-link-alt"&gt;&lt;/i&gt;&lt;/sup&gt;&lt;/a&gt;, &lt;a href="https://heron.apache.org"target="_blank"&gt;Heron&lt;sup&gt;&lt;i class="fas fa-external-link-alt"&gt;&lt;/i&gt;&lt;/sup&gt;&lt;/a&gt;, &lt;a href="https://bookkeeper.apache.org"target="_blank"&gt;BookKeeper&lt;sup&gt;&lt;i class="fas fa-external-link-alt"&gt;&lt;/i&gt;&lt;/sup&gt;&lt;/a&gt;, and several others. On all of those projects I worked as some combination of tech writer, web designer, and build system &amp;ldquo;plumbing&amp;rdquo; person (i.e. the person in charge of making sure that the documentation inputs are converted into the right outputs and that those outputs are shipped to the right place).&lt;/p&gt;
&lt;p&gt;In other words, I&amp;rsquo;ve seen as much documentation sausage being made as just about anyone in our industry. And I hate to say it but my experience has led me to the firm conclusion that our documentation tools are fundamentally broken for many common use cases. In this post I&amp;rsquo;ll explain why I feel this way. In the forthcoming part 2, I&amp;rsquo;ll point to what I think could be a more sound path.&lt;/p&gt;</description></item><item><title>Tract: a Hugo theme for ambitious documentation projects</title><link>https://lucperkins.dev/blog/introducing-tract/</link><pubDate>Mon, 02 Dec 2019 00:00:00 +0000</pubDate><author>lucperkins@gmail.com (Luc Perkins)</author><guid>https://lucperkins.dev/blog/introducing-tract/</guid><description>&lt;p&gt;Hello! I wanted to tell you all about an open source project I&amp;rsquo;m working on that I&amp;rsquo;m pretty excited about. It&amp;rsquo;s called &lt;a href="https://tract-docs.dev"target="_blank"&gt;Tract&lt;sup&gt;&lt;i class="fas fa-external-link-alt"&gt;&lt;/i&gt;&lt;/sup&gt;&lt;/a&gt; and it&amp;rsquo;s a &lt;a href="https://gohugo.io"target="_blank"&gt;Hugo&lt;sup&gt;&lt;i class="fas fa-external-link-alt"&gt;&lt;/i&gt;&lt;/sup&gt;&lt;/a&gt; theme for large documentation projects. I aim to release version 0.1.0 by the end of 2019. In the meantime, check out the &lt;a href="https://tract-docs.dev"target="_blank"&gt;current home page&lt;sup&gt;&lt;i class="fas fa-external-link-alt"&gt;&lt;/i&gt;&lt;/sup&gt;&lt;/a&gt; or a &lt;a href="https://tract-docs.dev/en/docs/getting-started"target="_blank"&gt;sample docs page&lt;sup&gt;&lt;i class="fas fa-external-link-alt"&gt;&lt;/i&gt;&lt;/sup&gt;&lt;/a&gt;.&lt;/p&gt;</description></item><item><title>Welcome to my blog!</title><link>https://lucperkins.dev/blog/welcome/</link><pubDate>Thu, 28 Nov 2019 00:00:00 +0000</pubDate><author>lucperkins@gmail.com (Luc Perkins)</author><guid>https://lucperkins.dev/blog/welcome/</guid><description>&lt;p&gt;All right folks, I&amp;rsquo;m doing it old school. I like &lt;a href="https://medium.com/@lperkins"target="_blank"&gt;Medium&lt;sup&gt;&lt;i class="fas fa-external-link-alt"&gt;&lt;/i&gt;&lt;/sup&gt;&lt;/a&gt; well enough, but I thought this would be a fun personal project and a chance to both flex my design muscles a little bit and gain full control over how I present information.&lt;/p&gt;
&lt;p&gt;&lt;strong&gt;Stay tuned!&lt;/strong&gt;&lt;/p&gt;</description></item></channel></rss>