<?xml version="1.0" encoding="UTF-8"?><rss xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:atom="http://www.w3.org/2005/Atom" version="2.0" xmlns:cc="http://cyber.law.harvard.edu/rss/creativeCommonsRssModule.html">
    <channel>
        <title><![CDATA[Stories by Drew Noll on Medium]]></title>
        <description><![CDATA[Stories by Drew Noll on Medium]]></description>
        <link>https://medium.com/@oheydrew?source=rss-45f69eccfcdc------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/2*7kIDxLVA8942s8afanICdA.png</url>
            <title>Stories by Drew Noll on Medium</title>
            <link>https://medium.com/@oheydrew?source=rss-45f69eccfcdc------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Thu, 19 Nov 2026 13:15:34 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@oheydrew/feed" rel="self" type="application/rss+xml"/>
        <webMaster><![CDATA[yourfriends@medium.com]]></webMaster>
        <atom:link href="http://medium.superfeedr.com/" rel="hub"/>
        <item>
            <title><![CDATA[ComposeConf Melbourne 2019 — A new Type of adventure]]></title>
            <link>https://medium.com/@oheydrew/composeconf-melbourne-2019-a-new-type-of-adventure-39e08c3cbfad?source=rss-45f69eccfcdc------2</link>
            <guid isPermaLink="false">https://medium.com/p/39e08c3cbfad</guid>
            <category><![CDATA[haskell]]></category>
            <category><![CDATA[tech-conference]]></category>
            <category><![CDATA[compose-conference]]></category>
            <category><![CDATA[elixir]]></category>
            <category><![CDATA[functional-programming]]></category>
            <dc:creator><![CDATA[Drew Noll]]></dc:creator>
            <pubDate>Sun, 15 Sep 2019 01:55:04 GMT</pubDate>
            <atom:updated>2019-09-15T02:09:06.918Z</atom:updated>
            <content:encoded><![CDATA[<h3>ComposeConf Melbourne 2019 — A new Type of adventure</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*nPxbTUVfAODw3r3m" /><figcaption>Compose Conf’s ‘LambdaTram’</figcaption></figure><p>A few people I’d run into over the last few months had started to talk about <a href="http://www.composeconference.org/2019-melbourne/">Compose Conf</a> — a small functional programming conference held in Melbourne, Australia. One python programmer I’d met previously at <a href="https://2019.pycon-au.org/">PyConAU</a> told me he was organising it, I met another friend another at a <a href="http://melbjs.com/">MelbJS</a> meetup who was going, ran into an old Coder Academy buddy who was volunteering, and some old coworkers of mine were attending. The buzz was starting up. Only thing was, <em>I didn’t think I’d be able to make it.</em></p><p>But! Then I asked my team lead where I work, and he helped facilitate me getting along to the event. Thanks, <a href="http://www.ourxplor.com/">Xplor</a>!</p><p>And so it was that I headed on down to good old RMIT Building 80- a venue I’d been to a few times (and indeed, snuck into once or twice to find quiet places to study/hide) on a dreary Melbourne morning to hang out with a bunch of programmers and (presumably) talk about code. I didn’t know what to expect- Would I know anyone? I’ve only just started in Elixir- would I keep up with the talks? Would I be out of my depth?</p><p>Upon arrival, any anxiety was immediately soothed. People were super friendly, I found some meetup-buddies, coworkers and new friends to chat to, and everyone was keen to catch up, chat, and get into some serious mathematical, functional nerdery 🤓</p><h3>The Talks</h3><h4>Ambrose Bonnaire-Sergeant — The Hidden Data Flow in Types</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*EXlgUyh2IZCuJJye" /><figcaption>…simple, right? :)</figcaption></figure><p>The first talk by Ambrose set the tone immediately; what followed was going to be a seriously in-depth and highly technical set of talks, which would constantly stretch out my brain and push the limits of my knowledge and understanding of the world of FP.</p><p>Ambrose kicked it off by deep-diving into something I’ve not had a lot of experience with as a programmer working with dynamic languages like Elixir, Ruby and JavaScript: Types, and type-theory, specifically in Clojure. Though my knowledge of this language and topic is mostly theoretical, the way Ambrose took us through it kept me engaged and entertained.</p><p>The talk focussed on using function types to interpret and infer the inner workings of a function that uses that type. He started by walking us through the basics of <a href="https://en.wikipedia.org/wiki/Type_inference">type inference</a> and some of the strategies employed in how this is done (see: <a href="https://en.wikipedia.org/wiki/Hindley%E2%80%93Milner_type_system">Hindley-Milner</a>, <a href="https://genericlanguage.wordpress.com/2010/08/30/let%C2%A0polymorphism/">let-polymorphism</a>) as a basis for understanding the talk, and then he took us through his work in using the data flow through functions to infer implementations inside these functions.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*PtJPBjG_QZJo1iSm" /><figcaption>Following data flow from input, to output, in a map function</figcaption></figure><p>This stuff was really eye-opening and interesting; whilst I can’t claim to be an expert, it was even easy for myself, a type-system novice, to follow the flow of the input data of a function, to the next function call, to the next, to the next, and in doing so come to an understanding of how that function worked. Ambrose took us deeper into how this can be practically applied to any function manually, a way to infer implementation on paper as if we were doing long division.</p><p>I specifically enjoyed his comment toward the end:</p><blockquote>“The best part is you can do this yourself! Seriously! Go find your favourite function, and try this at home!”</blockquote><p>😂 It got me thinking; <em>What is my favourite function?</em> (Spoilers: I think it might be <a href="https://codeburst.io/learn-understand-javascripts-reduce-function-b2b0406efbdc">reduce</a>)</p><h4>Svetlana Marina — Day-to-Day Property-Based Testing in Scala</h4><p>Next up, Svetlana Marina, with a talk as loaded full of programmer jokes as it was informative. Svetlana led us through a journey of property-based testing, more specifically related to a particular Scala package called ScalaCheck. From what I could infer from the talk, ScalaCheck uses property-based testing to generate large datasets and runs your tests thousands of times against a large range of data, attempting to catch edge cases in your code.</p><p>Even if I didn’t quite manage to grasp the Scala syntax on the few slides I had in front of me, the main takeaway I got from this is that in property-based testing, one doesn’t specify example inputs and outputs directly- instead defining the properties expected by the function and ScalaCheck (or, as I’ve since learned, <a href="https://hypothesis.works/articles/quickcheck-in-every-language/">many other types of QuickCheck engines</a>) then generates randomized input data to feed in and runs the tests hundreds, perhaps thousands of times.</p><p>Pretty nuts! But quite simple in practice. I found myself wondering, along with Svetlana as she pointed out in her talk, how common this actually is, or if anyone has time in their day to day to do it. I appreciated that she held a balanced opinion to when it was and wasn’t a useful strategy.</p><p>My favourite takeaway was her quick run of slides describing overall testing strategies in more plain-English catchphrases:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*dQqpHCTdeDznfjAyHaNSvA.jpeg" /><figcaption>Commutativity: Different Paths, Same Destination</figcaption></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*4ZdQY-r_CfhYoKXMRUu1eQ.jpeg" /><figcaption>Idempotence: The more things change, the more they stay the same</figcaption></figure><ul><li><a href="https://www.restapitutorial.com/lessons/idempotency.html">Idempotence</a>: “The more things change, the more they stay the same”</li><li><a href="https://medium.com/@wilsonsinquest/on-writing-tests-as-an-induction-proof-of-system-correctness-5ddae19207ca">Induction</a>: “Solve a smaller problem first”</li><li>Commutativity: “Different paths, same destination”</li><li>Multiple Implementation Strategies: “The Test Oracle”</li><li>E2E Test Journeys: “Hard to prove, Easy to verify”</li></ul><p>Some of these will stick around with me, especially the little Idempotence and Commutativity catchphrases. Thanks!</p><h4>Brendan Zabarauskas — Lost in a Universe of Types: My Adventures in Programming Languages</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*9XODziIT7JHe6hxT" /><figcaption>Brendan’s love for his work was contagious</figcaption></figure><p>Brendan’s stage manner was upbeat and entertaining, and his enthusiasm for the in-depth mathematical solutions to his programming problems was contagious, even if, unfortunately for me, I was a little lost on the specifics.</p><p>I won’t spend a lot of time on the specifics of this one, as a lot of it veered into realms I’m not particularly familiar with, but he did a good job of taking us through the complex issues he faced and tackled whilst writing software to analyse and implement <a href="https://scripts.sil.org/cms/scripts/page.php?site_id=nrsi&amp;id=IWS-Chapter08">binary TrueType Fonts</a>. The man’s clearly a genius, and the definitions alone for the font’s specification were enough to make my mind boggle. It was highly entertaining watching him work through and explain his findings.</p><h4>Jack Kelly — Reflex Outside the Browser</h4><p>Following was a talk by Jack Kelly which, despite it being not my field and despite fighting through my post-break food-coma, I managed to get more out of than I expected!</p><p>Starting with something I understood: an example of a card-game (Magic: The Gathering — now we’re talking!), Jack took us through <a href="https://en.wikipedia.org/wiki/Functional_reactive_programming">FRP</a>, or Functional Reactive Programming. This talk got pretty in-depth pretty quickly, focussing on a technology called Reflex, a way to interact with the DOM using FRP and Haskell.</p><p>Whilst a lot of this quickly passed beyond my realm of understanding- it laid out a good number of things for me to investigate: The above link to FRP itself, as well as more to look at inside <a href="https://github.com/reflex-frp/reflex-dom">reflex-FRP</a>.</p><h4>George Wilson — An Intuition for Propagators</h4><blockquote>“Thing is, I’m not even trying to sell you on propagators. I’m trying to sell you on the kind of thinking that this leads you toward. We had a model, and a problem, and we solved it, using mathematics!”</blockquote><p>The final talk in the morning before the post-lunch workshops was by George Wilson, an upbeat, excited and expressive functional programmer at the CSIRO’s Data61 FP Lab.</p><p>This one was entertaining — George took us back to a technology not widely implemented but fascinating nonetheless- the propagator model. This interesting system uses a concept called “Cells”, little pieces of state that get connected to independent stateless functions called “Propagators”, that tell them what to do, and in turn, react to the state of the cells they’re tied to, propagating messages throughout a network of cells.</p><p>Whilst not necessarily always efficient or super useful day-to-day, this was a novel look into a pretty in-depth and gnarly FP concept that almost looped fully back around to Object-Oriented programming, inside of Functional Programming itself. What a journey- and George gave us plenty of jokes and humour to keep us entertained throughout.</p><h3>”Crashkell” — A Haskell Workshop</h3><p>After lunch, we had the opportunity to choose from several workshops for the afternoon. I decided on Crashkell — a Haskell Crash course — I’ve been wanting to get into Haskell for some time now, and this looked like the perfect opportunity to do so!</p><p>The workshop itself was a BYO-laptop vibe with a REPL-based online workbook — all online in the browser, so there was no need to set up an environment and we could get straight into it. The workshop ran as a series of puzzles, of broken Haskell code which we had to fix, and get to run successfully. We’d have to use the error logs as well as some hints, and sometimes some help from others in the room to get by.</p><p>There were a few frustrations with puzzles that were focussed on syntax rather than logic, which ultimately led to a disappointed feeling when you’d struggle for a few minutes only to discover that the answer was a differently placed bracket or funky arrow syntax, but I appreciated the “Real World” nature of the troubleshooting and problem solving, as well as the collaboration with others working on the problems. I’d probably not work on these workshops alone though, without others versed in Haskell to help you through when the hints don’t guide quite well enough.</p><p>Overall I found it a lot of fun, though! I was impressed with Haskell’s verbosity and just how specific the language is, yet how quickly one can work through issues with syntax and implementation. As an Elixir dev, I didn’t actually find the syntax as challenging as I thought- turns out Elixir stole a lot more from Haskell than I thought! A lot of the fun was in working with my friends and colleagues on getting through the tougher challenges together.</p><h3>Final thoughts?</h3><p>After a full day of highly technical talks and an afternoon of programming in a new language, I was a bit exhausted, but glad to have experienced what I could from the conference. I’d met a bunch of new and lovely people, learned a <em>ton</em> and had a few pages in my notebook with things to follow up on.</p><p>Thanks, ComposeConf! I’ll see you next year, for sure 👍 🙌</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=39e08c3cbfad" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>