<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>xiv - Articles</title>
    <description>Thoughts, stories and ideas.</description>
    <link>
    </link>
    
      
      <item>
        <title>Home Project Workflow #fail</title>
        
          <description>&lt;blockquote&gt;
  &lt;p&gt;A colleague once told me that it is inherently difficult to be a good software architect consultant, as the contracts seldom extends long enough to analyze the outcome of the tough architectural choices made in the design and build phases of the project. This makes it difficult to become better, as you seldom get to see if your choices were good or bad.&lt;/p&gt;
&lt;/blockquote&gt;

</description>
        
        <pubDate>Mon, 21 Dec 2015 00:29:37 +0000</pubDate>
        <link>
        /home-project-workflow-fail</link>
        <guid isPermaLink="true">/home-project-workflow-fail</guid>
      </item>
      
    
      
      <item>
        <title>Docker workflow revisited</title>
        
          <description>&lt;blockquote&gt;
  &lt;p&gt;In the &lt;a href=&quot;http://blog.erikxiv.com/workflow-to-the-test/&quot;&gt;previous post&lt;/a&gt; I managed to verify the feasibility of my &lt;a href=&quot;http://blog.erikxiv.com/home-project-workflow/&quot;&gt;home project workflow&lt;/a&gt;, albeit with a few drawbacks coming to light. In this post I will address one of these; the need for installations on my local host.&lt;/p&gt;
&lt;/blockquote&gt;

</description>
        
        <pubDate>Fri, 10 Jul 2015 08:56:34 +0000</pubDate>
        <link>
        /workflow-revisited</link>
        <guid isPermaLink="true">/workflow-revisited</guid>
      </item>
      
    
      
      <item>
        <title>Workflow to the test</title>
        
          <description>&lt;h1 id=&quot;time-to-start-cracking&quot;&gt;Time to start cracking&lt;/h1&gt;

</description>
        
        <pubDate>Sun, 05 Jul 2015 21:49:39 +0000</pubDate>
        <link>
        /workflow-to-the-test</link>
        <guid isPermaLink="true">/workflow-to-the-test</guid>
      </item>
      
    
      
      <item>
        <title>Home Project Workflow</title>
        
          <description>&lt;blockquote&gt;
  &lt;p&gt;Well, its this time of year. A combination of inspiration and energy to start new development projects and a frustration due to the ratio I spend at scaffolding versus the ideas themselves. What to do? Why not ponder the yearly renewal of my workflow and tool-set?&lt;/p&gt;
&lt;/blockquote&gt;

</description>
        
        <pubDate>Mon, 22 Jun 2015 20:26:14 +0000</pubDate>
        <link>
        /home-project-workflow</link>
        <guid isPermaLink="true">/home-project-workflow</guid>
      </item>
      
    
      
      <item>
        <title>Neo4j on Synology</title>
        
          <description>&lt;blockquote&gt;
  &lt;p&gt;As &lt;a href=&quot;/docker-on-synology&quot;&gt;previously mentioned&lt;/a&gt; I seem to be able to host docker containers on my Synology NAS. Although preferring pure cloud services for my projects, there is a case to be made for the free hosting service of my NAS when there is no free hosting version of the service I want. Especially when it calculating the income-to-cost ratio of my standard million-dollar-ideas.&lt;/p&gt;
&lt;/blockquote&gt;

</description>
        
        <pubDate>Sat, 20 Jun 2015 20:01:26 +0000</pubDate>
        <link>
        /neo4j-on-synology</link>
        <guid isPermaLink="true">/neo4j-on-synology</guid>
      </item>
      
    
      
      <item>
        <title>Docker on Synology</title>
        
          <description>&lt;blockquote&gt;
  &lt;p&gt;I just found out that my NAS, a Synology DS412+, can host docker containers. It just went from a simple file storage and backup solution to a toy for proof-of-concepts. Next question: what will the capacity limit be?&lt;/p&gt;
&lt;/blockquote&gt;

</description>
        
        <pubDate>Sat, 20 Jun 2015 19:40:24 +0000</pubDate>
        <link>
        /docker-on-synology</link>
        <guid isPermaLink="true">/docker-on-synology</guid>
      </item>
      
    
  </channel>
</rss>
