<?xml version="1.0" encoding="UTF-8"?>
<feed xmlns="http://www.w3.org/2005/Atom" xml:lang="en">
<title type="text">Dario Magliocchetti</title>
<generator uri="https://github.com/mojombo/jekyll">Jekyll</generator>
<link rel="self" type="application/atom+xml" href="http://darioml.com/feed.xml" />
<link rel="alternate" type="text/html" href="http://darioml.com" />
<updated>2016-03-25T20:13:18+00:00</updated>
<id>http://darioml.com/</id>
<author>
  <name>Dario</name>
  <uri>http://darioml.com/</uri>
  
</author>


<entry>
  <title type="html"><![CDATA[Today I Learned - Brittle Tests]]></title>
 <link rel="alternate" type="text/html" href="http://darioml.com/til-tests/" />
  <id>http://darioml.com/til-tests</id>
  <updated>2016-03-24T00:00:00-00:00</updated>
  <published>2016-03-24T00:00:00+00:00</published>
  
  <author>
    <name>Dario</name>
    <uri>http://darioml.com</uri>
    <email></email>
  </author>
  <content type="html">
    &lt;p&gt;Testing is a fairly crucial part of building a scalable, reliable application. It’s impossible to confidently deploy simple (or complicated!) changes without being sure that nothing will break. And, working with &lt;a href=&quot;http://teachback.co.uk&quot;&gt;TeachBack&lt;/a&gt;, the last thing I want to do is end up spending my time fixing bugs introduced by fast development.&lt;/p&gt;

&lt;p&gt;However, there’s an interesting question to be asked. To what level do you test - and how brittle should those tests be? For instance, when you want to test a redux store, should you raise an action and make sure that the correct dispatches have been sent through the store? If you’re working on a frontend applications, should your tests cover the page layout and UX elements to a fine grain?&lt;/p&gt;

&lt;p&gt;Yes, this will help you make sure things don’t break when you ship. But brittle tests discourage refactoring, code cleanup and small changes. If I want to change the behavior of my application (or re-theme my website), I sure as hell don’t want to spend 30% of my time rewriting tests “just so they past”.&lt;/p&gt;

&lt;p&gt;What’s the solution here?&lt;/p&gt;

&lt;p&gt;I’m a strong believe that simple code tests itself. Splitting out code into small, manageable chunks makes it easier to conceptually test your code. This definitively doesn’t stop you from shipping bugs, but it reduces the environment in which &lt;em&gt;I&lt;/em&gt; write buggy code.&lt;/p&gt;

    &lt;p&gt;&lt;a href=&quot;http://darioml.com/til-tests/&quot;&gt;Today I Learned - Brittle Tests&lt;/a&gt; was originally published by Dario at &lt;a href=&quot;http://darioml.com&quot;&gt;Dario Magliocchetti&lt;/a&gt; on March 24, 2016.&lt;/p&gt;
  </content>
</entry>


<entry>
  <title type="html"><![CDATA[Set of Useful JS Libs]]></title>
 <link rel="alternate" type="text/html" href="http://darioml.com/set-of-useful-javascript-packages/" />
  <id>http://darioml.com/set-of-useful-javascript-packages</id>
  <updated>2016-02-24T00:00:00-00:00</updated>
  <published>2016-02-24T00:00:00+00:00</published>
  
  <author>
    <name>Dario</name>
    <uri>http://darioml.com</uri>
    <email></email>
  </author>
  <content type="html">
    &lt;p&gt;Nothing particular here, but I come across a number of useful javascript libs. I rarely need to use them right there and then. I don’t want to bury them in some unknown bookbar, and make them public.&lt;/p&gt;

&lt;h3 id=&quot;dragula&quot;&gt;Dragula&lt;/h3&gt;

&lt;p&gt;Drag and drop library. &lt;a href=&quot;http://bevacqua.github.io/dragula/&quot;&gt;github&lt;/a&gt;&lt;/p&gt;

    &lt;p&gt;&lt;a href=&quot;http://darioml.com/set-of-useful-javascript-packages/&quot;&gt;Set of Useful JS Libs&lt;/a&gt; was originally published by Dario at &lt;a href=&quot;http://darioml.com&quot;&gt;Dario Magliocchetti&lt;/a&gt; on February 24, 2016.&lt;/p&gt;
  </content>
</entry>


<entry>
  <title type="html"><![CDATA[TeachBack - New Website Launch]]></title>
 <link rel="alternate" type="text/html" href="http://darioml.com/teachback-website-launch/" />
  <id>http://darioml.com/teachback-website-launch</id>
  <updated>2015-03-04T00:00:00-00:00</updated>
  <published>2015-03-04T00:00:00+00:00</published>
  
  <author>
    <name>Dario</name>
    <uri>http://darioml.com</uri>
    <email></email>
  </author>
  <content type="html">
    &lt;p&gt;It’s been on my to-do list for a while now, but &lt;a href=&quot;http://teachback.co.uk&quot;&gt;TeachBack&lt;/a&gt; now finally has moved away from a wordpress installation to github pages &amp;amp; jekyll. Now, I’m able to push the &lt;em&gt;ever so infrequent&lt;/em&gt; blog posts to the website without having to remember &lt;strong&gt;another&lt;/strong&gt; set of login details&lt;sup id=&quot;fnref:1&quot;&gt;&lt;a href=&quot;#fn:1&quot; class=&quot;footnote&quot;&gt;1&lt;/a&gt;&lt;/sup&gt;, dynamically give permissions, and easily work on the website without bothering with custom wordpress plugins.&lt;/p&gt;

&lt;p&gt;The move was fairly painless. I’ve &lt;a href=&quot;https://github.com/darioml/votepascal.com&quot;&gt;previously&lt;/a&gt; worked &lt;a href=&quot;http://labs.hailocab.com/&quot;&gt;on jekyll&lt;/a&gt;, but I felt I couldn’t give enough effort to design a website in an evening. I came across a great theme from &lt;a href=&quot;http://mmistakes.github.io/minimal-mistakes/&quot;&gt;Michael Rose&lt;/a&gt;, which needed only a few mods to adapt it to our needs. I manually moved over the few blog posts from our wordpress installation (thought I’m sure something great such as &lt;a href=&quot;https://github.com/benbalter/wordpress-to-jekyll-exporter&quot;&gt;this&lt;/a&gt; could be used for a larger moved), and hit &lt;code class=&quot;highlighter-rouge&quot;&gt;git push&lt;/code&gt;.&lt;/p&gt;

&lt;p&gt;Voila!&lt;/p&gt;

&lt;p&gt;I can only but recommend using Jekyll for blogs and semi-static websites&lt;sup id=&quot;fnref:2&quot;&gt;&lt;a href=&quot;#fn:2&quot; class=&quot;footnote&quot;&gt;2&lt;/a&gt;&lt;/sup&gt;. The flexibility and simplicity it offers (&lt;em&gt;ignoring ruby&lt;/em&gt;) surpasses anything else I’ve worked with. Add on top of that the bonus of not having to worry about deployment, and there is nothing to dislike.&lt;/p&gt;

&lt;div class=&quot;footnotes&quot;&gt;
  &lt;ol&gt;
    &lt;li id=&quot;fn:1&quot;&gt;
      &lt;p&gt;Oh, and I’m also now not paying $12/month for a VPS to hold a wordpress website! &lt;a href=&quot;#fnref:1&quot; class=&quot;reversefootnote&quot;&gt;&amp;#8617;&lt;/a&gt;&lt;/p&gt;
    &lt;/li&gt;
    &lt;li id=&quot;fn:2&quot;&gt;
      &lt;p&gt;Posts, comments, etc are all possible. Limitations come in when you need to write customer server software or interact with a database. &lt;a href=&quot;#fnref:2&quot; class=&quot;reversefootnote&quot;&gt;&amp;#8617;&lt;/a&gt;&lt;/p&gt;
    &lt;/li&gt;
  &lt;/ol&gt;
&lt;/div&gt;

    &lt;p&gt;&lt;a href=&quot;http://darioml.com/teachback-website-launch/&quot;&gt;TeachBack - New Website Launch&lt;/a&gt; was originally published by Dario at &lt;a href=&quot;http://darioml.com&quot;&gt;Dario Magliocchetti&lt;/a&gt; on March 04, 2015.&lt;/p&gt;
  </content>
</entry>

</feed>
