<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Me, thinking out loud</title>
    <link>https://blog.straughan.org/</link>
    <description>Recent content on Me, thinking out loud</description>
    <generator>Hugo -- gohugo.io</generator>
    <language>en-GB</language>
    <lastBuildDate>Sat, 26 Jan 2019 17:28:38 +0100</lastBuildDate>
    
	<atom:link href="https://blog.straughan.org/index.xml" rel="self" type="application/rss+xml" />
    
    
    <item>
      <title>Finally catchup on ES6</title>
      <link>https://blog.straughan.org/post/finally-catch-up-on-es6/</link>
      <pubDate>Sat, 26 Jan 2019 17:28:38 +0100</pubDate>
      
      <guid>https://blog.straughan.org/post/finally-catch-up-on-es6/</guid>
      <description>&lt;h1 id=&#34;overview----omit-in-toc---&#34;&gt;Overview &lt;!-- raw HTML omitted --&gt;&lt;/h1&gt;
&lt;p&gt;I have managed to avoid most of the gnarly details of javascript beyond ES5 for many years. Unfortunately a side project has driven me to finally take it on board. These are my notes, gleaned mostly by reading &lt;a href=&#34;https://hacks.mozilla.org/category/es6-in-depth/page/2/&#34;&gt;ES6 In Depth&lt;/a&gt; from Jason Orendorff of Mozilla.&lt;/p&gt;
&lt;p&gt;I now know enough to be &lt;em&gt;more&lt;/em&gt; dangerous.&lt;/p&gt;</description>
    </item>
    
    <item>
      <title>Learning Bash</title>
      <link>https://blog.straughan.org/post/learning-bash/</link>
      <pubDate>Mon, 27 Nov 2017 17:20:20 +0000</pubDate>
      
      <guid>https://blog.straughan.org/post/learning-bash/</guid>
      <description>&lt;h1 id=&#34;overview&#34;&gt;Overview&lt;/h1&gt;
&lt;p&gt;Historically I&#39;m a Windows developer (C/C++/C#). I&#39;ve been using more and more Linux tooling and, day by day, the Linux learning is creeping in. A massive sprawling knowledge space, unfamiliar to me. But over and over again there are some basic bash scripting techniques I need, this is them.&lt;/p&gt;</description>
    </item>
    
    <item>
      <title>Behaviours not Errors</title>
      <link>https://blog.straughan.org/post/behaviours-not-errors/</link>
      <pubDate>Mon, 18 Sep 2017 21:53:01 +0100</pubDate>
      
      <guid>https://blog.straughan.org/post/behaviours-not-errors/</guid>
      <description>Overview Recently, I have been thinking about my preference for structured logging (details on this in to-be-written entry). A trivial but significant aspect of this, is that once you have switched to structured logging, markers like INFO, DEBUG, ERROR,&amp;hellip; don&#39;t help. Simply grouping such a wide range of code paths into these categories is insufficient for any kind of analysis.
What is an error? An error is a local failure scenario that you don&#39;t currently understand - our continuous improvement process for error handling aims to move all these anomalies in the system from unknown to known.</description>
    </item>
    
    <item>
      <title>There are Only 4 reasons to write software</title>
      <link>https://blog.straughan.org/post/4-reasons-to-write-code/</link>
      <pubDate>Tue, 23 May 2017 22:56:47 +0100</pubDate>
      
      <guid>https://blog.straughan.org/post/4-reasons-to-write-code/</guid>
      <description>&lt;h1 id=&#34;reasons-to-write-code&#34;&gt;Reasons to write code;&lt;/h1&gt;
&lt;ol&gt;
&lt;li&gt;Make money&lt;/li&gt;
&lt;li&gt;Save money&lt;/li&gt;
&lt;li&gt;Stay out of jail&lt;/li&gt;
&lt;li&gt;For fun&lt;/li&gt;
&lt;/ol&gt;</description>
    </item>
    
    <item>
      <title>Refactoring with VS Code</title>
      <link>https://blog.straughan.org/post/multiple-cursors/</link>
      <pubDate>Tue, 18 Oct 2016 07:51:11 +0100</pubDate>
      
      <guid>https://blog.straughan.org/post/multiple-cursors/</guid>
      <description>&lt;h1 id=&#34;efficient-refactoring&#34;&gt;Efficient Refactoring&lt;/h1&gt;
&lt;p&gt;Whilst watching an episode of Francesc Campoy&#39;s &lt;em&gt;just for func&lt;/em&gt; series I noticed that there was a major feature of VS Code that was going unused. Multiple cursors. This is one of the biggest productivitiy features of modern text editors.&lt;/p&gt;</description>
    </item>
    
    <item>
      <title>The coding interview</title>
      <link>https://blog.straughan.org/post/coding-interviews/</link>
      <pubDate>Tue, 30 Aug 2016 07:47:35 +0100</pubDate>
      
      <guid>https://blog.straughan.org/post/coding-interviews/</guid>
      <description>&lt;h1 id=&#34;the-code-interview&#34;&gt;The code interview&lt;/h1&gt;
&lt;p&gt;The interviews I want to write about are specifically face-to-face code interviews. I have interviewed quite a few people over the years and too many of them seem to be going out of their way to fail. So these are my tips on how not to rule yourself out.&lt;/p&gt;</description>
    </item>
    
    <item>
      <title>It&#39;s called Software for a reason</title>
      <link>https://blog.straughan.org/post/its-called-software/</link>
      <pubDate>Tue, 02 Aug 2016 07:25:46 +0100</pubDate>
      
      <guid>https://blog.straughan.org/post/its-called-software/</guid>
      <description>&lt;h1 id=&#34;making-a-change&#34;&gt;Making a change&lt;/h1&gt;
&lt;p&gt;When making a change to an existing piece of software I think there are broadly 2 options;&lt;/p&gt;
&lt;ol&gt;
&lt;li&gt;Get in and out, change as little as possible&lt;/li&gt;
&lt;li&gt;Restructure the code to fit the new requirement&lt;/li&gt;
&lt;/ol&gt;</description>
    </item>
    
    <item>
      <title>Contact</title>
      <link>https://blog.straughan.org/contact/</link>
      <pubDate>Tue, 05 Jul 2016 22:32:11 +0100</pubDate>
      
      <guid>https://blog.straughan.org/contact/</guid>
      <description>Best off, start with http://twitter.com/nearlyAdam</description>
    </item>
    
    <item>
      <title>About</title>
      <link>https://blog.straughan.org/about/</link>
      <pubDate>Tue, 05 Jul 2016 22:27:37 +0100</pubDate>
      
      <guid>https://blog.straughan.org/about/</guid>
      <description>The Internet home for my thoughts (at least the ones that I am [a] able to capture and [b] willing to share) and possibly projects.</description>
    </item>
    
    <item>
      <title>Get ready</title>
      <link>https://blog.straughan.org/post/get-ready/</link>
      <pubDate>Tue, 05 Jul 2016 18:01:48 +0100</pubDate>
      
      <guid>https://blog.straughan.org/post/get-ready/</guid>
      <description>&lt;h1 id=&#34;new-blog&#34;&gt;New blog&lt;/h1&gt;
&lt;p&gt;This is &lt;em&gt;attempt N&lt;/em&gt; (where N is larger than I&#39;d like) of actually setting up and adding content to a blog and or article based web site.&lt;/p&gt;</description>
    </item>
    
    <item>
      <title></title>
      <link>https://blog.straughan.org/adam-straughan-cv/</link>
      <pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate>
      
      <guid>https://blog.straughan.org/adam-straughan-cv/</guid>
      <description>Adam Straughan, BEng Profile Experienced software development team lead with a solid history of delivering valuable, robust software solutions to clients. A leadership approach that enables teams to deliver together. A development approach to allow continuous delivery of value.
Key Skills  Team Lead, provide space and direction to enable teams to succeed. Architecture and Design, a wide range of experience from embedded C, Windows device drivers, traditional web sites through to distributed services and event based systems.</description>
    </item>
    
  </channel>
</rss>