<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Posts on Jesse Dearing</title>
    <link>https://jesse.dev/post/</link>
    <description>Recent content in Posts on Jesse Dearing</description>
    <generator>Hugo</generator>
    <language>en</language>
    <lastBuildDate>Sun, 03 Mar 2019 09:05:26 -0800</lastBuildDate>
    <atom:link href="https://jesse.dev/post/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Giving VSCode a go</title>
      <link>https://jesse.dev/post/20190226-giving-vscode-a-go/</link>
      <pubDate>Sun, 03 Mar 2019 09:05:26 -0800</pubDate>
      <guid>https://jesse.dev/post/20190226-giving-vscode-a-go/</guid>
      <description>&lt;p&gt;I tried &lt;a href=&#34;https://code.visualstudio.com/&#34;&gt;VSCode&lt;/a&gt; for 3 weeks just because I had&#xA;been working a lot with Terraform and other members of my team mentioned the&#xA;various plugins available for Terraform. I found using VSCode to be a really&#xA;wonderful experience.&lt;/p&gt;</description>
    </item>
    <item>
      <title>Complex Adaptive Systems in Software</title>
      <link>https://jesse.dev/post/20180427_complex_adaptive_systems/</link>
      <pubDate>Wed, 13 Jun 2018 16:57:00 -0700</pubDate>
      <guid>https://jesse.dev/post/20180427_complex_adaptive_systems/</guid>
      <description>&lt;p&gt;Resilience engineering is becoming a required practice as people begin to expect&#xA;services to be available nearly 100% of the time. We have the same requirements&#xA;of the systems that sustain us: ecosystems, anatomical systems. Our world is one&#xA;complex adaptive system after another.&lt;/p&gt;</description>
    </item>
    <item>
      <title>5 CLI Tools all software engineers should know about</title>
      <link>https://jesse.dev/post/20161114_5_cli_tools_all_software_engineers_should_know_about/</link>
      <pubDate>Mon, 14 Nov 2016 22:07:24 -0800</pubDate>
      <guid>https://jesse.dev/post/20161114_5_cli_tools_all_software_engineers_should_know_about/</guid>
      <description>&lt;p&gt;The following CLI tools, I have found to be extremely useful when dealing with&#xA;systems to quickly find the information I need. Please note that all these&#xA;commands are being run from OS X and are the BSD commands not the GNU commands&#xA;that typically ship with a standard Linux distro.&lt;/p&gt;</description>
    </item>
    <item>
      <title>Fixed vs. Growth System Failures</title>
      <link>https://jesse.dev/post/20161019-fixed-vs-growth-system-failures/</link>
      <pubDate>Wed, 19 Oct 2016 11:06:08 -0800</pubDate>
      <guid>https://jesse.dev/post/20161019-fixed-vs-growth-system-failures/</guid>
      <description>&lt;p&gt;The concept of Mindset based on the work: &lt;a href=&#34;http://amzn.to/2dEPR9M&#34;&gt;Mindset by Dr. Carol S. Dweck,&#xA;Ph.D.&lt;/a&gt;&#xA;has been around for some time now, but recently I was thinking about root cause&#xA;analyses meant as a tool for learning. Revisiting the John Allspaw post: The&#xA;&lt;a href=&#34;http://www.kitchensoap.com/2014/11/14/the-infinite-hows-or-the-dangers-of-the-five-whys/&#34;&gt;Infinite Hows (or, the Dangers Of The Five&#xA;Whys)&lt;/a&gt; make me start thinking about&#xA;what makes a lot of people look at postmortems as a checkbox or paperwork and&#xA;not value them as learning experiences.&lt;/p&gt;</description>
    </item>
    <item>
      <title>Go is for .Close()’ers</title>
      <link>https://jesse.dev/post/20161004-go-is-for-closers/</link>
      <pubDate>Tue, 04 Oct 2016 10:35:32 -0800</pubDate>
      <guid>https://jesse.dev/post/20161004-go-is-for-closers/</guid>
      <description>&lt;p&gt;The &lt;code&gt;Close()&lt;/code&gt; method is important to the reliability of a running program and&#xA;it&amp;rsquo;s not easy to tell when it should be used.&lt;/p&gt;</description>
    </item>
    <item>
      <title>Who’s Running that on my System: Case of the stolen CPU</title>
      <link>https://jesse.dev/post/20160916-whos-running-that-on-my-system/</link>
      <pubDate>Fri, 16 Sep 2016 01:11:56 -0700</pubDate>
      <guid>https://jesse.dev/post/20160916-whos-running-that-on-my-system/</guid>
      <description>&lt;p&gt;Last week, I found myself needing to find what application a query was&#xA;originating from. My typical method for doing this is searching through source&#xA;code before I eventually get angry that I can’t find the query originating from&#xA;an ORM and start drafting an email decreeing that all applications get distinct&#xA;logins to the database that I’ll never send because who is going to listen&#xA;anyway.&lt;/p&gt;&#xA;&lt;p&gt;I had an idea for how I can track a query all the way back to the process that&#xA;accessed it and I even scripted it.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
