<?xml version="1.0" encoding="utf-8" standalone="yes" ?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Blogs on A blog by Gregor Petrin</title>
    <link>http://blog.petrin.co/blog/</link>
    <description>Recent content in Blogs on A blog by Gregor Petrin</description>
    <generator>Hugo -- gohugo.io</generator>
    <language>en-us</language>
    <lastBuildDate>Thu, 28 Dec 2017 21:31:12 +0100</lastBuildDate>
    
	<atom:link href="http://blog.petrin.co/blog/index.xml" rel="self" type="application/rss+xml" />
    
    
    <item>
      <title>Enjoy your magic responsibly</title>
      <link>http://blog.petrin.co/blog/enjoy-your-magic-responsibly/</link>
      <pubDate>Thu, 28 Dec 2017 21:31:12 +0100</pubDate>
      
      <guid>http://blog.petrin.co/blog/enjoy-your-magic-responsibly/</guid>
      <description>I&amp;#8217;ve tolerated too much magic in my code. Metaclass programming, convention over configuration, lazy loaded proxies, &amp;lt;insert your own here&amp;gt; techniques that promise to make your prototyping even quicker and your short code even shorter.
 Magic sure looks sexy in short tutorials.
 In a complex product with complex requirements that needs to be maintained over the long run, however, it tends to cause more trouble than it&amp;#8217;s worth. I&amp;#8217;ve mostly enjoyed working with Grails, AngularJS and Hibernate, to name just some examples, but I&amp;#8217;ve had their magic spells change behaviour after dependency updates, perfectly sensible code refuse to work for arcane reasons, otherwise excellent tools utterly confused by all that magic and having to fight frameworks because I needed to do some small thing differently.</description>
    </item>
    
    <item>
      <title>Gradle&#39;s subprojects can&#39;t declare subprojects</title>
      <link>http://blog.petrin.co/blog/gradle-subprojects-cannot-declare-subprojects/</link>
      <pubDate>Wed, 27 Dec 2017 07:32:12 +0100</pubDate>
      
      <guid>http://blog.petrin.co/blog/gradle-subprojects-cannot-declare-subprojects/</guid>
      <description>Looking at Gradle&amp;#8217;s documentation on subprojects their support for nesting subprojects looks very powerful. I&amp;#8217;ve glanced over their water, whale and krill examples many times when I was looking for this or that and I never really noticed that the examples were always water/bluewhale or water/krill but never water/whale/bluewhale.
 While such a setup is possible it must be done in a specific way. In my opinion, it is far too easy to end up with an invalid setup without Gradle complaining - a setup that will work very poorly without the developer knowing the real reasons for this.</description>
    </item>
    
    <item>
      <title>A New Blog</title>
      <link>http://blog.petrin.co/blog/a-new-blog/</link>
      <pubDate>Tue, 26 Dec 2017 11:10:12 +0100</pubDate>
      
      <guid>http://blog.petrin.co/blog/a-new-blog/</guid>
      <description>Since the beginning of this month I&amp;#8217;ve been enjoying the wonderful Advent of Code - every day at 6 o&amp;#8217;clock a wonderful programming puzzle would unlock for me to enjoy with my morning coffee.
 Today, one day after christmas and a holiday around here, I&amp;#8217;m missing the puzzles already so I decided to start a new blog. This is not the first blog I&amp;#8217;ve started, though perhaps I will be more persistent this time.</description>
    </item>
    
  </channel>
</rss>