<?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 Marc Cataford on Medium]]></title>
        <description><![CDATA[Stories by Marc Cataford on Medium]]></description>
        <link>https://medium.com/@mcataford?source=rss-7dfcd039c9cd------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*E2taPDMDn19bX_yNKDNzRw.png</url>
            <title>Stories by Marc Cataford on Medium</title>
            <link>https://medium.com/@mcataford?source=rss-7dfcd039c9cd------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Sun, 22 Nov 2026 03:19:41 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@mcataford/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[Waiting for Jenkins]]></title>
            <link>https://medium.com/@mcataford/waiting-for-jenkins-6e70838b021c?source=rss-7dfcd039c9cd------2</link>
            <guid isPermaLink="false">https://medium.com/p/6e70838b021c</guid>
            <category><![CDATA[jenkins]]></category>
            <category><![CDATA[visualization]]></category>
            <category><![CDATA[performance]]></category>
            <category><![CDATA[open-source]]></category>
            <category><![CDATA[continuous-integration]]></category>
            <dc:creator><![CDATA[Marc Cataford]]></dc:creator>
            <pubDate>Fri, 01 Feb 2019 22:03:30 GMT</pubDate>
            <atom:updated>2019-02-01T22:03:30.255Z</atom:updated>
            <content:encoded><![CDATA[<p>People often say <em>Move fast, break things</em> when talking about software development when they should really say <em>Move fast, break things and wait for CI</em>. As projects grow in size, time spent building and testing on continuous integration systems like <em>Jenkins</em>, <em>CircleCI</em> and <em>Travis</em> balloons and tends to quickly outgrow time spent writing code. Even though build machines handle the heavy lifting of CI, a long, unoptimized build process still represents a bottleneck for development velocity: you can’t merge before you pass CI.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/413/0*hpzkVX-ZNW71ZhjW" /><figcaption><a href="https://xkcd.com/303/"><em>Relevant XKCD</em></a></figcaption></figure><p>If you disregard some of the more complex aspects of CI, you can reduce build pipeline optimization to two main actionable items: maximizing parallelization and minimizing the duration of sequential build steps. The more you can do at once and the shorter the resulting steps are, the faster your build goes through. However, while improving on these factors depends on CI features and on the code being run, applying either efficiently and strategically requires some insights about the pipeline’s behaviour and tools to get those insights are not necessarily available. To tackle this problem, we turned to Jenkins and its plugin API to create <a href="https://jenkinstimeline.com/docs/overview">the Jenkins Timeline</a>, an open-source pipeline visualization solution to your slow builds.</p><h3>What can it do for me?</h3><p>By visualizing the Jenkins build process as a Gantt chart, the timeline allows you to quickly hone in on the stages or steps that are holding up your builds so that you can invest your optimization efforts where they will have the most impact. It can also help you estimate the potential gains of parallelizing certain steps of your build process. By quickly looking at your pipeline’s timeline, you can know right away if spending the next day or so tinkering with your CI configuration will yield good results.</p><p>Beyond what the plugin gives you out-of-the-box, it is also a budding open source project. If it does not fit your use case, you can easily suggest changes that would bridge the gap, making it better for everyone.</p><h3>Where can I get my hands on it?</h3><p>The project is currently hosted on <a href="https://github.com/tophat/jenkins-timeline-plugin"><strong>Github</strong></a>, has <a href="https://jenkinstimeline.com/"><strong>its own website</strong></a> and is available on the <a href="https://plugins.jenkins.io/pipeline-timeline"><strong>Jenkins Marketplace</strong></a>. Don’t hesitate to reach out on Github if you’d like to get your hands dirty and contribute!</p><h3>Shout out to contributors</h3><p>It’s important to shout out <a href="https://github.com/tophat/jenkins-timeline-plugin#contributors">the contributors</a> that made the project possible so far. After all, the saying “It takes a village to raise a child” applies to many things, including open source; it’s exponentially easier to write great software in projects supported by great people. Special thanks, in no particular order, to <a href="https://github.com/jakebolam"><strong>Jake Bolam</strong></a>, <a href="https://github.com/brandonbaksh"><strong>Brandon Baksh</strong></a>, <a href="https://github.com/sjoanes"><strong>Savio Joanes</strong></a>, <a href="https://github.com/chrono"><strong>Martin Ringehahn</strong></a>, <a href="https://github.com/syavash"><strong>Siavash Mahmoudian</strong></a> and <a href="https://github.com/sdcosta"><strong>Shouvik D’Costa</strong></a> for pitching in in different capacities over the past few months to help prop this up!</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=6e70838b021c" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Cash might be king, but they don’t care (and it’s not necessarily a good thing)]]></title>
            <link>https://medium.com/@mcataford/cash-might-be-king-but-they-dont-care-and-it-s-not-necessarily-a-good-thing-4b34243592c5?source=rss-7dfcd039c9cd------2</link>
            <guid isPermaLink="false">https://medium.com/p/4b34243592c5</guid>
            <category><![CDATA[technology]]></category>
            <category><![CDATA[big-data]]></category>
            <category><![CDATA[opinion]]></category>
            <category><![CDATA[privacy]]></category>
            <category><![CDATA[economy]]></category>
            <dc:creator><![CDATA[Marc Cataford]]></dc:creator>
            <pubDate>Tue, 26 Dec 2017 17:52:03 GMT</pubDate>
            <atom:updated>2017-12-26T19:43:14.376Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*j9e1QD72TnIsMQA3FuxjcQ.jpeg" /><figcaption><a href="http://alphastockimages.com/">via Alpha Stock Images</a></figcaption></figure><p>On Christmas day, The New York Times published an <a href="https://www.nytimes.com/2017/12/25/nyregion/no-cash-money-cashless-credit-debit-card.html">interesting piece</a> on cashless business, lauding the move toward a cashless society. Few New York eateries are discussed, and in each case, customers note how unusual it is for physical currency to be <em>non grata. </em>While phasing out cold hard cash in favour of credit/debit cards and mobile app-based payment streamlines the customers’ experience purchasing goods and services and simplifies the bookkeeping processes on the providers’ side, the emphasis on convenience obscures bigger concerns, namely the evergrowing reliance on technology and the gradual erosion of privacy, which were left unaddressed.</p><h4>“In any case, the machine was down.”</h4><p>One can easily argue that technology is already embedded in our daily lives and that we are <em>already </em>totally dependent on gadgets. After all, I’m sure I’m not the only one to instinctively reach for my mobile phone whenever a question crosses my mind and to do most of my banking online. However, it is also important to mention the idea that <em>redundancy</em> is paramount in building and maintaining robust systems — absolute reliance on failure-prone devices isn’t good.</p><p>When hospitals integrated electronics in their routine healthcare procedures, back-up generators were added to medical facilities to ensure that a power outage wouldn’t be synonymous with a break in care that could result in deaths. Reducing the robustness of the systems that allow us to trade with each other certainly isn’t as ominous as tripping on someone’s artificial respirator power cord, but it remains a threat nonetheless.</p><p>When systems fail without any alternative measures in place, tricky situations may arise. In the case of sales, there are not that many options:</p><blockquote>Her friend ordered a vegan chocolate cone. He was told he could not pay with cash. He handed over his credit card. There was a problem with the card reader, or maybe the Wi-Fi. In any case, the machine was down. The cashier apologized and said the ice cream was on the house.</blockquote><p>Losing a snack sale’s worth of revenue because of a technical failure is trivial, but the event described is emblematic of something we should never forget: <em>if it can break, it probably will — better be ready</em>. Earlier this year, we saw <a href="https://techcrunch.com/2017/02/28/amazon-aws-s3-outage-is-breaking-things-for-a-lot-of-websites-and-apps/">AWS fail</a> and bring down a decent chunk of the internet with it. The cause? <a href="https://aws.amazon.com/message/41926/">Human error</a>. When it happened <a href="https://www.wired.com/2011/04/lessons-amazon-cloud-failure/">back in 2011</a>, a resounding criticism of the services that were affected was that they had failed to design for failure and had put all their eggs in the same basket. The cashless businesses described by the NYT did it anyway.</p><p>On the ground, away data centers, failure also happens. The Venn diagram of shopkeepers and tech-savvy folks is far from being a circle; when the point-of-sale system fails, troubleshooting options are scarce. Calling the providers’ technical support line is usually the way to go, but this usually involves significant delays — this is when a “Cash only” sign would be stuck to the front window.</p><p>Instead of having to trust a single service to perform properly, cashless transactions require dozens: the service that validates payment, the internet service provider, the platforms on which all of those services live, the physical cabling that connects them together and the point-of-sale machine that accepts payment, all of which are prone to failure independently of the others.</p><p>Two customers interviewed in the article summarized it best:</p><blockquote>“My thought was, sometimes the analog world works better than the digital.”</blockquote><p>Having the option to deal in “analog” terms is useful. After all, how many times did you glance at your phone only to realize you were on battery saver with no outlet in sight, or that you had forgotten your cards on the kitchen counter after cleaning out your pockets? The redundancy of having a handful of dollar bills and a few quarters at the bottom of your bag is definitely useful when these things happen.</p><p>After seeing <a href="https://www.nytimes.com/2015/03/18/business/premera-blue-cross-says-data-breach-exposed-medical-data.html">companies</a> <a href="https://www.nytimes.com/2015/03/18/business/premera-blue-cross-says-data-breach-exposed-medical-data.html">fail</a> to secure their data in the past years, what can we infer about their ability to keep their systems up?</p><h4>As much privacy as a goldfish in a bowl</h4><p>It is surprising that privacy did not make the cut for an article about cashless shops in an age ruled by Big Data. Everything that happens in the digital world can be documented: devices’ logs can have a wealth of information on how they were used in recent history and any resource shared over a network bounces from machine to machine to get to its destination, any of which can collect metrics on what is happening.</p><p>Cashless transactions produce a trove of data with which keen analysts could find out who buys what at which frequency and where. On the surface, this data might seem inconsequential, who cares if Big Data knows about my candy habit? The problem lies in what can be <em>inferred</em> from the data.</p><p>Say you buy candy on a regular basis with your preferred cashless payment system. Over time, a ledger of your sugar cravings grows in a dark corner of some third-party data center. What if this data could be used to evaluate how healthy you are or even, how much you should pay for health insurance? In 2014, The NYT published <a href="https://www.nytimes.com/roomfordebate/2014/04/14/dna-and-insurance-fate-and-risk">a very interesting debate series</a> about insurers and the prospects of using DNA sequencing to guide insurance policies — the same general ideas can be transposed to cashless payment in the present argument. Individual transactions are generally inconsequential, but when they are accumulated, <em>trends </em>appear, and from trends can emerge inference.</p><p>On an even greater level, that data could be used for social credit schemes like <a href="https://www.wired.com/story/age-of-social-credit/?mbid=social_twitter">the one China is slowly but surely pushing on its citizens</a>. Combined with the data already put online voluntarily through services like Facebook, Twitter and Instagram, it is not far-fetched to see cashless transactions as a way to add another dimension to your profile as seen by companies and governments.</p><p>That data might not be safe either: both the public and the private sector has a terrible track record when it comes to keeping intruders at bay. A quick look at <a href="http://www.informationisbeautiful.net/visualizations/worlds-biggest-data-breaches-hacks/">Information is Beautiful’s breach tracker</a> reveals that breaches are common across the board: safety is elusive.</p><p>Despite reservations, cashless transactions are not all bad. They do simplify purchases (paying for your new laptop with a suitcase full of cash is impractical, albeit delightfully dramatic) and make online shipping possible, which is amazing. The point isn’t the demonize cashless systems, but to keep options open.</p><p><a href="http://money.cnn.com/2017/07/14/news/companies/visa-no-cash-restaurant-initiative/index.html">A Visa executive</a> described cashlessness as “freedom from carrying cash,” a level of positiveness that was expected coming from the party that stands to profit from the transition (credit card companies collect transaction fees, therefore a cashless society would be great for them). I’d rather phrase it as a move toward a system that is friendlier to Orwellian dystopias.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=4b34243592c5" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>