<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Graeme Pietersz</title>
    <link>https://pietersz.net/</link>
    <description>Writing on IT, finance &amp; strategy — tagged and interlinked.</description>
    <generator>Hugo</generator>
    <language>en-gb</language>
    <atom:link href="https://pietersz.net/rss.xml" rel="self" type="application/rss+xml" />
    <lastBuildDate>Mon, 10 Feb 2020 15:44:29 +0000</lastBuildDate>
    <item>
      <title>So, you think you are not in a technology business?</title>
      <link>https://pietersz.net/posts/tech-business/</link>
      <pubDate>Mon, 10 Feb 2020 15:44:29 +0000</pubDate>
      <guid>https://pietersz.net/posts/tech-business/</guid>
      <description>&lt;p&gt;Many years ago the CEO of a large transport company&lt;sup id=&#34;fnref:1&#34;&gt;&lt;a href=&#34;#fn:1&#34; class=&#34;footnote-ref&#34; role=&#34;doc-noteref&#34;&gt;1&lt;/a&gt;&lt;/sup&gt; told me that he regarded their IT as a key competitive advantage. IT should be a vital part of reducing costs, or improving the product or service, or generating leads in almost any business. What opportunities do you have to make technology a competitive advantage?&lt;/p&gt;</description>
    </item>
    <item>
      <title>Why your business (probably) has code quality problems</title>
      <link>https://pietersz.net/posts/code-quality-problems/</link>
      <pubDate>Mon, 27 Jan 2020 17:30:35 +0000</pubDate>
      <guid>https://pietersz.net/posts/code-quality-problems/</guid>
      <description>&lt;p&gt;I am very much an advocates of developing custom systems in pursuit of productivity and competitive advantage, but in this post I am discussing one of the draw backs of doing so. In fact, most businesses rely on custom code in some form or another, but do not really realise it.&lt;/p&gt;</description>
    </item>
    <item>
      <title>What determines success and failure on the web?</title>
      <link>https://pietersz.net/posts/web-success-failure/</link>
      <pubDate>Wed, 18 Sep 2019 14:52:11 +0100</pubDate>
      <guid>https://pietersz.net/posts/web-success-failure/</guid>
      <description>&lt;p&gt;What makes a web site (or a web app) a success or a failure? Having seen a lot of successes and failures I find there are a few common types of business website that have different risks and determinants of success:&lt;/p&gt;</description>
    </item>
    <item>
      <title>What&#39;s your disaster recover plan?</title>
      <link>https://pietersz.net/posts/whats-your-disaster-recover-plan/</link>
      <pubDate>Thu, 13 Jun 2019 05:01:43 +0100</pubDate>
      <guid>https://pietersz.net/posts/whats-your-disaster-recover-plan/</guid>
      <description>&lt;p&gt;A business can be destroyed by losing its data. I have known even losing the data on a single person&amp;rsquo;s hard drive to be very expensive, and losing your servers can be much worse. You need to think about backups, continuity, hardware. I have taken a server out of a bomb blasted building and it worked - but it might not have.&lt;/p&gt;</description>
    </item>
    <item>
      <title>Technical debt from a business persepective</title>
      <link>https://pietersz.net/posts/technical-debt-from-a-business-perspective/</link>
      <pubDate>Tue, 16 Apr 2019 18:41:40 +0100</pubDate>
      <guid>https://pietersz.net/posts/technical-debt-from-a-business-perspective/</guid>
      <description>&lt;p&gt;Technical debt tends to be talked about, and worried about, more by developers than by those running a business or looking after its finance. The problem is that not taking it into account &lt;strong&gt;will&lt;/strong&gt; lead to bad decisions.&lt;/p&gt;</description>
    </item>
    <item>
      <title>Why your website should be ugly</title>
      <link>https://pietersz.net/posts/ugly-website/</link>
      <pubDate>Tue, 19 Mar 2019 10:35:42 +0000</pubDate>
      <guid>https://pietersz.net/posts/ugly-website/</guid>
      <description>&lt;p&gt;Most people (out side the industry anyway) assume that web sites should look good, and an aesthetically good website will produce better results than an ugly one. This is not true, and many of the things that make a website look good will tend to make it worse for users.&lt;/p&gt;</description>
    </item>
    <item>
      <title>The problem with SaaS</title>
      <link>https://pietersz.net/posts/problem-saas/</link>
      <pubDate>Thu, 14 Mar 2019 19:25:46 +0000</pubDate>
      <guid>https://pietersz.net/posts/problem-saas/</guid>
      <description>&lt;p&gt;SaaS (software as a service) is extremely popular right now, and it can solve a lot of problems. It means someone else takes responsibility for maintenance and security. Of course nothing is ever &lt;em&gt;that&lt;/em&gt; easy a win.&lt;/p&gt;&#xA;&lt;p&gt;So, what are the problems? Our experience is that there are three, two of which are closely linked:&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
