<?xml version="1.0" encoding="utf-8"?>
<feed xmlns="http://www.w3.org/2005/Atom">
    <title><![CDATA[DomCode]]></title>
    <link href="/atom.xml" rel="self"/>
    <link href="/"/>
    <updated>2016-01-03T17:48:31+01:00</updated>
    <id>/</id>
        <generator uri="http://sculpin.io/">Sculpin</generator>
            <entry>
            <title type="html"><![CDATA[Writing Code That Lasts]]></title>
            <link href="/videos/2015/11/24/writing-code-that-lasts"/>
            <updated>2015-11-24T00:00:00+01:00</updated>
            <id>/videos/2015/11/24/writing-code-that-lasts</id>
            <content type="html"><![CDATA[<p><em>This video was recorded and hosted by the Hogeschool Utrecht. You can view it <a href="https://www.weblectures.hu.nl/p2gplayer/Player.aspx?id=err5qx">on their recordings site</a>.</em></p>

<p>As developers we write code everyday, only to frown at it a week after that. Why do we have such a hard time with code written by others and ourselves, this raging desire to rewrite everything we see? Writing code that survives the test of time and self judgment is a matter of clarity and simplicity. Let's talk about growing, learning and improving our code with calisthenics, readability and good design.</p>
]]></content>
        </entry>
            <entry>
            <title type="html"><![CDATA[Data Migration: How not to leave a legacy]]></title>
            <link href="/videos/2015/06/30/data-migration-how-not-to-leave-a-legacy"/>
            <updated>2015-06-30T00:00:00+02:00</updated>
            <id>/videos/2015/06/30/data-migration-how-not-to-leave-a-legacy</id>
            <content type="html"><![CDATA[<p>When a company moves to a new software architecture, they usually prefer to keep the relevant data from their old system(s). This quickly gets complicated, because data is dirty, unreliable, there's usually a lot of it, the old architecture looks nothing like the new one, and in some cases the Dutch Central Bank kindly requires you to prove you've done it right down to the last cent.</p>

<p>In this talk, I'll talk about migrating data from a big, complicated system to a big, complicated system. I will use insurance systems as my example, because that's what I work with, but the problems we encounter are pretty general.</p>

<p>We will not get extremely technical, but cover a few examples of the following topics:</p>

<ul>
<li>The many steps of data migration: how not to go insane when you're changing everything</li>
<li>Performance: streamlining the biggest batch-job your client will ever run</li>
<li>How to prove completeness and accuracy</li>
</ul>
]]></content>
        </entry>
            <entry>
            <title type="html"><![CDATA[ClojureScript and React.js]]></title>
            <link href="/videos/2015/05/26/clojurescript-and-reactjs"/>
            <updated>2015-05-26T00:00:00+02:00</updated>
            <id>/videos/2015/05/26/clojurescript-and-reactjs</id>
            <content type="html"><![CDATA[<p>Over the last few years we have seen the rise of browser  applications. Instead of rendering all UI server side, JavaScript driven client applications are now being widely adopted. While JavaScript is a flexible and powerful language, it has its shortcomings. This is where languages that compile to JavaScript step in. ClojureScript is one of them and offers its own powerful features to the front end developer.</p>

<p>React is a JavaScript library for creating declarative UIs. It was  created by Facebook to simplify writing applications consisting of many components. React allows you to write the UI as a function of state.</p>

<p>It turns out ClojureScript loves React. In this talk you will see how these two fit together, using the Reagent library as an example.</p>
]]></content>
        </entry>
            <entry>
            <title type="html"><![CDATA[Developing a Reactive Process Manager, Twice]]></title>
            <link href="/videos/2015/02/24/developing-a-reactive-process-manager-twice"/>
            <updated>2015-02-24T00:00:00+01:00</updated>
            <id>/videos/2015/02/24/developing-a-reactive-process-manager-twice</id>
            <content type="html"><![CDATA[<p>This talk focuses on using the Actor Model, both in Scala with Akka and then using an Akka-like toolkit supporting Actor Model in C# with .NET.</p>
]]></content>
        </entry>
    </feed>