<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:content="http://purl.org/rss/1.0/modules/content/">
  <channel>
    <title>Innovation on Chris Harding</title>
    <link>https://418b6483.chrisharding-io.pages.dev/categories/innovation/</link>
    <description>Recent content in Innovation on Chris Harding</description>
    <image>
      <title>Chris Harding</title>
      <url>https://418b6483.chrisharding-io.pages.dev/%3Clink%20or%20path%20of%20image%20for%20opengraph,%20twitter-cards%3E</url>
      <link>https://418b6483.chrisharding-io.pages.dev/%3Clink%20or%20path%20of%20image%20for%20opengraph,%20twitter-cards%3E</link>
    </image>
    <generator>Hugo -- 0.147.7</generator>
    <language>en-us</language>
    <lastBuildDate>Mon, 18 May 2020 18:02:03 +0000</lastBuildDate>
    <atom:link href="https://418b6483.chrisharding-io.pages.dev/categories/innovation/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Building a calendar in Swift</title>
      <link>https://418b6483.chrisharding-io.pages.dev/posts/building-a-calendar-in-swift/</link>
      <pubDate>Mon, 18 May 2020 18:02:03 +0000</pubDate>
      <guid>https://418b6483.chrisharding-io.pages.dev/posts/building-a-calendar-in-swift/</guid>
      <description>&lt;p&gt;In this post, I wanted to walk through an approach I used when building a calendar view in Swift for an iOS app I’m working on. The requirements were as follows:&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;Should start from the current day, and then scroll backwards through time&lt;/li&gt;
&lt;li&gt;Each month is it’s own section, with corresponding header&lt;/li&gt;
&lt;li&gt;Days should be a selectable square cell, and we should have 3 days on each row&lt;/li&gt;
&lt;li&gt;The grid should take up as much screen real estate as possible&lt;/li&gt;
&lt;li&gt;It should be memory efficient&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;And with any luck, it will look something like this&amp;hellip;&lt;/p&gt;</description>
    </item>
    <item>
      <title>The Lean Startup</title>
      <link>https://418b6483.chrisharding-io.pages.dev/posts/the-lean-startup/</link>
      <pubDate>Sat, 16 Jun 2018 13:23:03 +0000</pubDate>
      <guid>https://418b6483.chrisharding-io.pages.dev/posts/the-lean-startup/</guid>
      <description>&lt;p&gt;Following in the same vein as 
&lt;a href=&#34;https://chrisharding.io/the-hard-thing-about-hard-things&#34; title=&#34;The Hard Thing About Hard Things&#34; target=&#34;_blank&#34; rel=&#34;nofollow noopener noreferrer&#34;&gt;The Hard Thing About Hard Things&lt;/a&gt;
, I am going to discuss The Lean Startup by 
&lt;a href=&#34;https://en.wikipedia.org/wiki/Eric_Ries&#34; title=&#34;Eric Ries&#34; target=&#34;_blank&#34; rel=&#34;nofollow noopener noreferrer&#34;&gt;Eric Ries&lt;/a&gt;
. Devised in 2008 by Ries, the Lean methodology aims to put science around becoming an entrepreneur along with fostering an innovation environment. Ries demonstrates his model predominantly through examples of the company he helped to build, 
&lt;a href=&#34;https://en.wikipedia.org/wiki/IMVU&#34; title=&#34;IMVU&#34; target=&#34;_blank&#34; rel=&#34;nofollow noopener noreferrer&#34;&gt;IMVU&lt;/a&gt;
. One of the core tenants of Lean is maximising the value delivered to customers. By achieving maximum value, Lean states you will cut out wastage and ultimately thrive against competition. In order to achieve this, the concept of &lt;em&gt;Validated Learning&lt;/em&gt; is introduced. Validated Learning is a process whereby you make assumptions, test and then measure their impact. This process allows you to obtain empirical evidence that your assumptions were indeed correct.&lt;/p&gt;</description>
    </item>
    <item>
      <title>What’s the deal with Hackathons?</title>
      <link>https://418b6483.chrisharding-io.pages.dev/posts/whats-the-deal-with-hackathons/</link>
      <pubDate>Sat, 17 Mar 2018 10:48:03 +0000</pubDate>
      <guid>https://418b6483.chrisharding-io.pages.dev/posts/whats-the-deal-with-hackathons/</guid>
      <description>&lt;p&gt;We’ve all heard the term Hackathon and some of us have likely been to one. They are the stuff of legend – 48 hour coding sessions fuelled by pizza and energy drinks. Events which have spawned long lists of multi-million dollar success stories such as Carousell and 
&lt;a href=&#34;https://groupme.com/&#34; target=&#34;_blank&#34; rel=&#34;nofollow noopener noreferrer&#34;&gt;GroupME&lt;/a&gt;
. But what are they, and how do you get your manager to agree to running one?&lt;/p&gt;
&lt;h3 id=&#34;lets-think-about-jeff&#34;&gt;Let’s think about Jeff&lt;/h3&gt;
&lt;p&gt;Jeff? Let me introduce you to Jeff. Jeff has been working at BigCorp now for several years. He’s a talented mid-level engineer working on a long running piece of enterprise software. You know the kind of software we’re talking about here. The kind of software that was designed by a plethora of contractors who have long since left. The kind of software that started life as a Winforms app, spun out as a Service, switched to MVVM, implemented several different UX frameworks and now resembles Sloth from The Goonies. As you can imagine, Jeff is fairly dissatisfied at work. If you were to ask him why, well he’d have a list longer than his arm. The tech is archaic – all his friends are playing with the latest .js library and he’s merely keeping the life support running. This means he is not getting opportunity to learn, develop and challenge himself. He also works alone and feels abandoned on this project. This has led to him no longer believing in the mission of the team or the values of BigCorp.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
