<?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 Emile Silvis on Medium]]></title>
        <description><![CDATA[Stories by Emile Silvis on Medium]]></description>
        <link>https://medium.com/@emilesilvis?source=rss-bcba718628ae------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/0*tiWZUJYABITSh7Wg.png</url>
            <title>Stories by Emile Silvis on Medium</title>
            <link>https://medium.com/@emilesilvis?source=rss-bcba718628ae------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Sun, 22 Nov 2026 13:11:15 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@emilesilvis/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[14 lessons for helping people make good software]]></title>
            <description><![CDATA[<div class="medium-feed-item"><p class="medium-feed-snippet">I&#x2019;ve spent the last year as a software engineering manager for teams building a new product. Our tribe (the group of teams) was part of a&#x2026;</p><p class="medium-feed-link"><a href="https://medium.com/swlh/14-lessons-for-helping-people-make-good-software-4950ef974013?source=rss-bcba718628ae------2">Continue reading on The Startup »</a></p></div>]]></description>
            <link>https://medium.com/swlh/14-lessons-for-helping-people-make-good-software-4950ef974013?source=rss-bcba718628ae------2</link>
            <guid isPermaLink="false">https://medium.com/p/4950ef974013</guid>
            <category><![CDATA[software-development]]></category>
            <category><![CDATA[software-engineering]]></category>
            <category><![CDATA[agile]]></category>
            <category><![CDATA[scrum]]></category>
            <dc:creator><![CDATA[Emile Silvis]]></dc:creator>
            <pubDate>Wed, 04 Sep 2019 12:47:05 GMT</pubDate>
            <atom:updated>2019-09-05T17:10:19.551Z</atom:updated>
        </item>
        <item>
            <title><![CDATA[Why ‘courage’ is a Scrum value and ‘being right’ is not]]></title>
            <description><![CDATA[<div class="medium-feed-item"><p class="medium-feed-image"><a href="https://medium.com/@emilesilvis/why-courage-is-a-scrum-value-and-being-right-is-not-76027fadcd26?source=rss-bcba718628ae------2"><img src="https://cdn-images-1.medium.com/max/620/0*uN61A0VSOgrbbVws.jpg" width="620"></a></p><p class="medium-feed-snippet">I often see situations like this in software teams:</p><p class="medium-feed-link"><a href="https://medium.com/@emilesilvis/why-courage-is-a-scrum-value-and-being-right-is-not-76027fadcd26?source=rss-bcba718628ae------2">Continue reading on Medium »</a></p></div>]]></description>
            <link>https://medium.com/@emilesilvis/why-courage-is-a-scrum-value-and-being-right-is-not-76027fadcd26?source=rss-bcba718628ae------2</link>
            <guid isPermaLink="false">https://medium.com/p/76027fadcd26</guid>
            <category><![CDATA[scrum-master]]></category>
            <category><![CDATA[scrum]]></category>
            <category><![CDATA[software-development]]></category>
            <category><![CDATA[agile]]></category>
            <dc:creator><![CDATA[Emile Silvis]]></dc:creator>
            <pubDate>Mon, 17 Sep 2018 14:31:49 GMT</pubDate>
            <atom:updated>2018-09-17T14:35:07.687Z</atom:updated>
        </item>
        <item>
            <title><![CDATA[A thought experiment: let’s add a new role to scrum — the craft master]]></title>
            <link>https://medium.com/@emilesilvis/a-thought-experiment-lets-add-a-new-role-to-scrum-the-craft-master-f2dc1bdfc1e8?source=rss-bcba718628ae------2</link>
            <guid isPermaLink="false">https://medium.com/p/f2dc1bdfc1e8</guid>
            <category><![CDATA[software-development]]></category>
            <category><![CDATA[agile]]></category>
            <category><![CDATA[scrum]]></category>
            <dc:creator><![CDATA[Emile Silvis]]></dc:creator>
            <pubDate>Wed, 06 Jun 2018 10:26:58 GMT</pubDate>
            <atom:updated>2018-06-06T10:26:58.252Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1000/1*kHmnrCSiC0YFoQptKs9j3g.jpeg" /><figcaption><a href="http://www.shutterstock.com/pic-246475696/stock-photo-overhead-view-of-a-set-of-old-wood-working-tools.html?src=-iQJ5UthdwFDoP7zA6rKzg-1-0">Tools</a> image via Shutterstock</figcaption></figure><p>I recently read <a href="https://www.lambdacambridge.com/blog/how-scrum-disempowers-developers-and-destroys-agile">an article</a> about how scrum disempowers developers due to its focus on value rather than technical excellence. This is something that resonates with me, so to <a href="https://en.wikipedia.org/wiki/Intuition_pump">“pump” my intuition</a> I want to do a little thought experiment where we try to stay within the scrum universe, but try to solve the main problem (developers being disempowered by scrum) by modifying the scrum framework.</p><p>As the author of the article states, “Scrum has a master, product has an owner, but no-one is empowered to advocate for development priorities.” To remedy this, let’s add a new role to scrum called the <strong>craft master</strong>. The craft master guides the team to understand their <a href="https://en.wikipedia.org/wiki/Software_craftsmanship">work as a craft</a>, and to help them reflect and improve on it. This person does not necessarily have to be an individual contributor (much like the scrum master). The craft master has excellent technical leadership skills, deep technical knowledge and keeps abreast of what’s happening in the world of “software craftsmanship”. The craft master makes sure that the team’s notion of quality and craftsmanship manifest in the Definition of Done, and <a href="https://medium.com/@emilesilvis/definitions-of-done-should-be-as-visible-as-your-product-backlog-4d9d6c2b4b9c">brings the Definition of Done to the foreground as an integral part of scrum</a>.</p><p><strong>Would the craft master empower developers?</strong></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=f2dc1bdfc1e8" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Definitions of Done should be a co-star — not a supporting actor]]></title>
            <description><![CDATA[<div class="medium-feed-item"><p class="medium-feed-snippet">Something I realised recently (which I knew in theory but ignored in practice) is that reminding teams that they are the ones responsible&#x2026;</p><p class="medium-feed-link"><a href="https://medium.com/@emilesilvis/definitions-of-done-should-be-as-visible-as-your-product-backlog-4d9d6c2b4b9c?source=rss-bcba718628ae------2">Continue reading on Medium »</a></p></div>]]></description>
            <link>https://medium.com/@emilesilvis/definitions-of-done-should-be-as-visible-as-your-product-backlog-4d9d6c2b4b9c?source=rss-bcba718628ae------2</link>
            <guid isPermaLink="false">https://medium.com/p/4d9d6c2b4b9c</guid>
            <category><![CDATA[scrum]]></category>
            <category><![CDATA[agile]]></category>
            <dc:creator><![CDATA[Emile Silvis]]></dc:creator>
            <pubDate>Thu, 17 May 2018 14:45:54 GMT</pubDate>
            <atom:updated>2018-07-26T13:10:55.132Z</atom:updated>
        </item>
        <item>
            <title><![CDATA[I did a workshop on systems thinking]]></title>
            <link>https://medium.com/@emilesilvis/i-did-a-workshop-on-systems-thinking-14e932285781?source=rss-bcba718628ae------2</link>
            <guid isPermaLink="false">https://medium.com/p/14e932285781</guid>
            <category><![CDATA[systems-thinking]]></category>
            <dc:creator><![CDATA[Emile Silvis]]></dc:creator>
            <pubDate>Wed, 16 May 2018 09:59:44 GMT</pubDate>
            <atom:updated>2018-05-16T10:01:33.120Z</atom:updated>
            <content:encoded><![CDATA[<p>In April, <a href="https://www.linkedin.com/in/rolandflemm/">Roland</a> and I presented a <a href="https://mixitconf.org/2018/if-you-can-draw-the-problem-you-can-solve-it-systems-thinking-made-practical">workshop</a> on systems thinking at the <a href="http://mixitconf.org/">MiXiT conference</a> in Lyon. Check out the <a href="https://docs.google.com/presentation/d/1Dj_6PPAaipV7B3JXCQdzjm8711AUP5vlWCWKwm_V7j4">presentation</a> and <a href="https://docs.google.com/document/d/1OHspWOyicETmp26PlV4biXLCjvm82SS7qyltwQtVyDk/edit?usp=sharing">case study</a> we used. Also check out this <a href="https://medium.com/@emilesilvis/a-curated-list-of-systems-thinking-resources-b883f1f02c7">list of systems thinking resources</a>.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*DvUDGP2yIUrDq55e8GTKWA.jpeg" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*XDlk3KV-S9WUEd89LRAWxw.jpeg" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*gtF9ilLWPZepbXiEhs6Ndw.jpeg" /><figcaption>People drawing causal loop diagrams</figcaption></figure><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=14e932285781" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[A curated list of systems thinking resources]]></title>
            <link>https://medium.com/@emilesilvis/a-curated-list-of-systems-thinking-resources-b883f1f02c7?source=rss-bcba718628ae------2</link>
            <guid isPermaLink="false">https://medium.com/p/b883f1f02c7</guid>
            <category><![CDATA[systems-thinking]]></category>
            <dc:creator><![CDATA[Emile Silvis]]></dc:creator>
            <pubDate>Tue, 03 Apr 2018 14:04:21 GMT</pubDate>
            <atom:updated>2018-04-03T14:04:21.009Z</atom:updated>
            <content:encoded><![CDATA[<h3>Books</h3><ul><li><a href="https://www.amazon.com/gp/product/1603580557">Thinking in Systems: A Primer</a> (Meadows, 2008)</li><li><a href="https://www.amazon.com/gp/product/0385517823">The Fifth Discipline</a> (Senge, 2006)</li><li>A <a href="https://dzone.com/articles/top-15-systems-thinking-books">list</a> of more books on systems thinking</li></ul><h3>Websites</h3><ul><li><a href="http://www.systems-thinking.org/">http://www.systems-thinking.org</a></li><li><a href="https://thesystemsthinker.com/">https://thesystemsthinker.com</a></li><li><a href="https://systemsandus.com/">https://systemsandus.com</a></li></ul><h3>Tools</h3><ul><li><a href="https://insightmaker.com/">https://insightmaker.com</a></li><li><a href="http://ncase.me/loopy/">http://ncase.me/loopy</a></li><li><a href="https://kumu.io/">https://kumu.io</a></li><li><a href="https://sysdea.com/">https://sysdea.com</a></li><li><a href="https://www.iseesystems.com/store/products/stella-architect.aspx">https://www.iseesystems.com/store/products/stella-architect.aspx</a></li></ul><h3>Videos</h3><ul><li><a href="https://www.youtube.com/watch?v=OqEeIG8aPPk">If Russ Ackoff had given a TED Talk…</a></li></ul><h3>Courses</h3><ul><li><a href="https://online.unschools.co/courses/systems-thinking">Unschool Systems Thinking course</a></li></ul><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=b883f1f02c7" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[What I have learned from running a small software consultancy]]></title>
            <link>https://medium.com/@emilesilvis/what-i-have-learned-from-running-a-small-software-consultancy-a838f37e599c?source=rss-bcba718628ae------2</link>
            <guid isPermaLink="false">https://medium.com/p/a838f37e599c</guid>
            <category><![CDATA[innovation]]></category>
            <category><![CDATA[startup]]></category>
            <category><![CDATA[lessons-learned]]></category>
            <dc:creator><![CDATA[Emile Silvis]]></dc:creator>
            <pubDate>Sun, 30 Oct 2016 03:26:01 GMT</pubDate>
            <atom:updated>2016-10-30T03:26:01.092Z</atom:updated>
            <content:encoded><![CDATA[<p>Me and two friends started <a href="http://www.glio.co.za/">Glio</a> in September 2012. By day Glio was a consultancy, offering website development (mainly with <a href="http://www.wordpress.org/">WordPress</a> on <a href="http://en.wikipedia.org/wiki/LAMP_(software_bundle)">LAMP</a>) and graphic design services. By night Glio tried to be an incubator — we hashed out hypotheses and ran lean experiments, but unfortunately nothing sustainable ever emerged from these endeavours.</p><p>We finally shut Glio down sometime at the end of 2014. It goes without saying that I learnt loads during these two years. This post attempts to chronicle these learnings.</p><ul><li>You’re in for the long haul. Despite what Silicon Valley might make you think, building a company is going take time. At times, it’s going to be boring and unglamorous. It’s definitely going to be hard work. Make sure that you realise the gravity of this, and make doubly sure that your partners realise it.</li><li>Separate your role as an owner from your role as an employee. As a owner it’s expected of you to bring leadership to the table. As an employee, it’s expected that you do quality work and that you are remunerated in return. Don’t confuse the two roles. Working 60 hours a week doesn’t make a good owner. Leadership, vision and care makes you a good owner.</li><li>Being really good at something does <em>not </em>mean that you should start your own business offering the skill. This speaks to the previous point. Being really good at X and getting paid for it, versus being really good at X and trying to sell it to unknown customers in a repeatable, sustainable and scalable way are two very different things. If you want to start your own business, make sure you’re the kind of person that loves the latter (otherwise go work for a boss).</li><li>It’s about the other eight business model building blocks too. The <a href="http://businessmodelgeneration.com/book?_ga=1.2654968.936281714.1430976779">Business Model Generation book</a> outlines nine building blocks that constitute a business model: value proposition, customers, customer relationships, sales channels, key activities, key resources, partners, cost structure and revenue streams. We often found ourselves in the situation where we focus only on one building block, value proposition, and completely ignore the other eight building blocks. If you’ve got a good idea, just build it and they will come, right? Wrong. You need all the other building blocks figured out too, and those are the hard ones.</li><li>The admin around starting and running a business can be complicated and tedious. Outsource these tasks where it’s worth it to do so (we did our own tax for a long time, and then outsourced it and haven’t looked back since).</li><li>Process is important, but values are more important. While a solid process will help you to control scope creep, for example, values will make you understand why it’s necessary to control scope in the first place. A good comprehension of the former without any presence of the latter will just cause headaches.</li></ul><p><em>Posted first at </em><a href="http://emilesilvis.com/2015/05/07/what-i-have-learned-from-running-a-small-software-consultancy/"><em>http://emilesilvis.com/2015/05/07/what-i-have-learned-from-running-a-small-software-consultancy/</em></a><em>.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=a838f37e599c" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Fix your budget, not your scope]]></title>
            <link>https://medium.com/@emilesilvis/fix-your-budget-not-your-scope-1eb14ae2e7eb?source=rss-bcba718628ae------2</link>
            <guid isPermaLink="false">https://medium.com/p/1eb14ae2e7eb</guid>
            <category><![CDATA[agile]]></category>
            <category><![CDATA[software-development]]></category>
            <dc:creator><![CDATA[Emile Silvis]]></dc:creator>
            <pubDate>Mon, 03 Oct 2016 06:42:14 GMT</pubDate>
            <atom:updated>2016-10-03T06:42:14.921Z</atom:updated>
            <content:encoded><![CDATA[<p>Many software projects take on the form of a <em>transaction</em> between vendor and customer. A transaction is an exchange of value. The vendor supplies software to the customer that solves some problem (scope), costs a certain amount (budget), by some date (schedule). The customer (hopefully) pays the vendor.</p><p>In any exchange of value, there exists the possibility of an <em>unfair</em> exchange. That is the situation where one party gains more value out of the transaction than the other for some reason. This possibility of unfairness is the <em>risk </em>associated to the transaction.</p><p>Typical contractual agreements between vendor and customer distributes risk in a certain way.</p><h3>Fixed bid</h3><p><em>Fixed bid</em> projects fix the scope, budget and timeline. To get to a fixed scope, budget and timeline, the following implicit assumptions are made:</p><ul><li>We can know the entire problem upfront, before we actually start the project (scope). The vendor can then design a feasible solution and work out how many people will be required to build it (cost) and how long this will take (time)</li><li>The problem space will never change (scope)</li></ul><p>In this model, all the risk is carried by the vendor, and very little risk is carried by the customer. In my opinion, the problem space is largely unknown. You discover the problem as you try solving it. By the same token, the solution has to be emergent. By trying to fix the scope upfront you do nothing more than speculate at a time when you know least about the problem and solution space. If the scope changes at all, the vendor would often carry the cost of the change.</p><h3>Time and materials</h3><p>With <em>time and materials</em> projects, the vendor simply charges the customer for any time spent. In this model, the customer carries all the risk. There are no guarantees for the customer around scope, budget and timelines. With time and materials the following implicit assumption are made:</p><ul><li>The vendor gets paid no matter what they produce</li><li>The customer has very little control over the process</li></ul><h3>Fixed budget, scope controlled</h3><p>At <a href="http://www.platform45.com/">Platform45</a> we’ve been experimenting with another alternative called <em>fixed budget, scope controlled</em> (I first saw this term used by <a href="https://atomicobject.com/">Atomic Object</a>). It attempts to distribute the risk between vendor and customer more evenly. It makes the following implicit assumption: there will <em>never</em> be enough time or money to build everything you want (fixed budget), therefore, you have to carefully control what you build (scope controlled). It is fundamentally a lean approach. It distributes risk evenly between vendor and customer because the vendor knows what constraints they need to work in to solve the problems (fixed budget), and customers get full control over what is being built (scope controlled). The ability to “control the scope” is loosely based on the following list of principles and practices.</p><ul><li>An estimation is a snapshot of understanding at a given point in time based on a given set of assumptions. Assumptions will change as we validate our learning (and so estimates will change)</li><li>Have short iterations / small batch sizes. This way you can handle changing assumptions and estimations without much waste</li><li>Vendor commits to solve a set of problems within budget, not to provide specific solutions. This allows the scope to be fluid enough to solve the problem within the budget constraints</li><li>There needs to be a continuous (at least once per iteration) negotiation between vendor and customer around priority for the next iteration</li><li>Vendor and customer continuously need to monitor budget and let that be a guide for prioritisation</li></ul><h3>It’s about being lean</h3><p>As mentioned before, most of the above boils down to a lean approach. As a vendor, some intentional education around this to the customer often helps a lot (I have often daydreamed about buying a stack of Lean Startup books and handing them out to new customers as mandatory reading).</p><p><em>First posted at </em><a href="http://emilesilvis.com/fix-your-budget-not-your-scope/">http://emilesilvis.com/fix-your-budget-not-your-scope/</a><em>.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=1eb14ae2e7eb" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Growth comes from real failure]]></title>
            <link>https://medium.com/@emilesilvis/growth-comes-from-real-failure-f4851e2d7af3?source=rss-bcba718628ae------2</link>
            <guid isPermaLink="false">https://medium.com/p/f4851e2d7af3</guid>
            <category><![CDATA[failure]]></category>
            <category><![CDATA[entrepreneurship]]></category>
            <category><![CDATA[growth]]></category>
            <dc:creator><![CDATA[Emile Silvis]]></dc:creator>
            <pubDate>Fri, 30 Sep 2016 03:26:02 GMT</pubDate>
            <atom:updated>2016-09-30T03:26:02.418Z</atom:updated>
            <content:encoded><![CDATA[<p>There is a certain narrative that is prevalent in contemporary startup cultures. Its story goes something along the lines of “failure is good so long as you’re learning from it”. On the surface it suggests speed and adaptiveness: fast-moving iterations driven by a tight feedback loop calibrated to avoid waste (who wants to spend hours building something nobody wants, right?). I’ll be the first to admit: it sounded smart, tenacious and brave.</p><p>But this version of failure has a subtle consequence: stagnancy. All of a sudden the act of failing becomes a mundane event, just one of many more to come. Failure loses its power. It strips you of the ability to question the bigger picture. Each time you fail, you are encouraged to take a different angle and try again (until you fail again, rinse, and repeat).</p><p>The truth is that real failure hurts. Real failure drives you into a dark corner and forces you to reconsider what you value in life. And then you grow.</p><p><em>First posted at </em><a href="http://emilesilvis.com/2014/10/15/growth-comes-from-real-failure/"><em>http://emilesilvis.com/2014/10/15/growth-comes-from-real-failure/</em></a><em>.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=f4851e2d7af3" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[A quick review of Exploring Everyday Things with R and Ruby]]></title>
            <link>https://medium.com/@emilesilvis/a-quick-review-of-exploring-everyday-things-with-r-and-ruby-10013ab953ae?source=rss-bcba718628ae------2</link>
            <guid isPermaLink="false">https://medium.com/p/10013ab953ae</guid>
            <category><![CDATA[book-review]]></category>
            <category><![CDATA[data-science]]></category>
            <dc:creator><![CDATA[Emile Silvis]]></dc:creator>
            <pubDate>Tue, 30 Aug 2016 03:26:02 GMT</pubDate>
            <atom:updated>2016-08-30T03:26:02.336Z</atom:updated>
            <content:encoded><![CDATA[<p>I’ve recently learned a lot about Ruby, and I’m also quite interested in <a href="http://www.r-project.org/">R</a>, a programming language for statistical computing. The book <a href="http://shop.oreilly.com/product/0636920022626.do">Exploring Everyday Things with R and Ruby</a> naturally piqued my interest.</p><p><strong>Overview of the book</strong></p><p>The first two chapters does a quick primer on Ruby and R respectively, and does a sufficient job to get you up and running with both Ruby and R.</p><p>The remaining six chapters each tries to “explore” a question. The main approach to “exploring” is a two-step process: 1) Use Ruby to extract data (typically stored as a CSV file) and 2) analyse this data with R.</p><p>The first chapter explores the amount of toilets required for a certain number of people. Ruby is used to simulate this population of people, the toilets and the queues forming outside the restroom.</p><p>The second chapter builds a basic model of a laissez-faire economy, and analyses the effects of price and demand.</p><p>The third chapter tries to glean insights from your email usage patterns, and uses a public collection of Enron emails to illustrate the points.</p><p>The fourth chapter lets you record your heartbeat and your pulse, and then extracts the information from the raw media files to visualise your heartbeat and heart rate.</p><p>The fifth chapter looks at the way birds and fish tend to flock together, and builds a <a href="http://en.wikipedia.org/wiki/Boids">Boids simulation</a> to explore <a href="http://en.wikipedia.org/wiki/Emergent_behaviour">emergent behaviour</a>.</p><p>The final chapter extends the previous model, but introduces several more elements into the simulation, including food, reproduction and evolution.</p><p><strong>The good</strong></p><ul><li>I think this is an excellent book for those who are curious, and wants to get a taste of doing some hands-on “exploration” of “everyday things”.</li><li>It gives you a collection of easy-to-understand and fun toy problems which you can explore on your own.</li><li>It’s a short and easy read.</li></ul><p><strong>The bad</strong></p><ul><li>Unfortunately the book is quite sparse on the <em>why </em>behind the analysis (the emphasis is really on exploring rather than analysing). Don’t expect to learn anything about statistical inference or probability theory. This is to be expected to some degree, however, since the book aims to be a layman’s introduction to using regular tools (Ruby and R) to explore regular stuff (building planning, the economy, flocking behaviour), and this it does really well. It’s the perfect appetiser, but it won’t satisfy you.</li><li>The code provided in the book is full of errors. To get any value out of these, you’ll have to clone the <a href="https://github.com/sausheong/everyday">GitHub</a> repository and work with that code.</li></ul><p><strong>I would give this book 4 out of 5. It’s a quick, fun whirlwind tour of using Ruby and R to prod at a variety of problems. Just don’t expect to scratch more than the tip of the iceberg.</strong></p><p><em>First posted at </em><a href="http://emilesilvis.com/2014/05/16/a-quick-review-of-exploring-everyday-things-with-r-and-ruby/"><em>http://emilesilvis.com/2014/05/16/a-quick-review-of-exploring-everyday-things-with-r-and-ruby/</em></a><em>.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=10013ab953ae" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>