<?xml version="1.0" encoding="UTF-8"?>
<feed xmlns="http://www.w3.org/2005/Atom">
  <id>http://grepthepipe.com/</id>
  <title>grep|</title>
  <updated>2012-11-28T20:15:19Z</updated>
  <link rel="alternate" href="http://grepthepipe.com/"/>
  <link rel="self" href="http://grepthepipe.com/feed/atom.xml"/>
  <author>
    <name>Leif Gensert</name>
    <uri>http://www.grepthepipe.com</uri>
  </author>
  <entry>
    <id>tag:grepthepipe.com,2012-11-28:/2012/11/28/rails-girls/</id>
    <title type="html">Words to erase from your vocabulary when coaching at RailsGirls</title>
    <published>2012-11-28T20:15:19Z</published>
    <updated>2012-11-28T10:27:08Z</updated>
    <author>
      <name>Leif Gensert</name>
      <uri>http://www.grepthepipe.com</uri>
    </author>
    <link rel="alternate" href="http://grepthepipe.com/2012/11/28/rails-girls/"/>
    <content type="html">&lt;p&gt;On October 13th 2012 I had the pleasure of being a coach at &lt;a href="http://railsgirls.com/"&gt;RailsGirls&lt;/a&gt; in&amp;nbsp;Munich.&lt;/p&gt;

&lt;p&gt;Having spent quite a fair I amount of time in front of a computer screen, I gatherd a lot of tchnical terms and been using them as if they were standard&amp;nbsp;vocabulary.&lt;/p&gt;

&lt;p&gt;But if you use terms like ‘continuous deployment’, ‘rapid prototyping’ or ‘static typing’ like talking about the weather you will have a hard time teaching programming to a beginner. Unfortunately a lot of strange terms will arise during an eight hour course of&amp;nbsp;web-development.&lt;/p&gt;

&lt;p&gt;Because avoiding these terms all together will be impossible, you should be at least be in the position to give a good explanation to each and every of the following expressions (in alphabetical&amp;nbsp;order):&lt;/p&gt;

&lt;ul&gt;
  &lt;li&gt;database&lt;/li&gt;
  &lt;li&gt;datatype&lt;/li&gt;
  &lt;li&gt;migration&lt;/li&gt;
  &lt;li&gt;route/routing&lt;/li&gt;
  &lt;li&gt;server&lt;/li&gt;
  &lt;li&gt;string&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;But keep in mind. While looking up the correct definition might be a good idea, it’s much more effective to find a good metaphor that fits 90% of the time (e.g. a string is ‘a line of&amp;nbsp;text’).&lt;/p&gt;
</content>
    <summary type="html">My experience on Rails Girls in Munich.
</summary>
  </entry>
  <entry>
    <id>tag:grepthepipe.com,2011-07-30:/2011/07/30/moved-to-nanoc/</id>
    <title type="html">moved from jekyll to nanoc</title>
    <published>2011-07-29T22:00:00Z</published>
    <updated>2011-07-29T22:00:00Z</updated>
    <author>
      <name>Leif Gensert</name>
      <uri>http://www.grepthepipe.com</uri>
    </author>
    <link rel="alternate" href="http://grepthepipe.com/2011/07/30/moved-to-nanoc/"/>
    <content type="html">&lt;p&gt;It’s been a while, since you’ve heard from me. In the meanwhile I managed to replace my static site generator. I successfully migrated my blog from &lt;a href="https://github.com/mojombo/jekyll/wiki"&gt;jekyll&lt;/a&gt; to &lt;a href="http://nanoc.stoneship.org/"&gt;nanoc&lt;/a&gt;. The main reason for this is that is that nanoc lets you use complete ruby (using erb) in the front-end instead of inventing some own markup&amp;nbsp;language.&lt;/p&gt;

&lt;p&gt;The migration was easier than expected. I kept the date like permalinks from jekyll using &lt;a href="http://groups.google.com/group/nanoc/browse_thread/thread/ba820e342a020602/4ab2b02d7ddcea0a"&gt;this reply&lt;/a&gt; in the user group. For the pagination I followed the &lt;a href="http://nanoc.stoneship.org/docs/6-guides/#paginating-articles"&gt;guide on the homepage&lt;/a&gt;. The &lt;code&gt;published&lt;/code&gt; attribute from jekyll was pretty easy to integrate as I’ve seen a feature in a &lt;a href="https://github.com/mgutz/nanoc3_blog/blob/master/Rules"&gt;blog example on github&lt;/a&gt;.&lt;/p&gt;

&lt;p&gt;These suggestions only left me with the migration of the articles, which was a piece of cake as the metadata syntax is almost the&amp;nbsp;same.&lt;/p&gt;
</content>
    <summary type="html">First blog post after a while. Changed my static site generator to nanoc.
</summary>
  </entry>
  <entry>
    <id>tag:grepthepipe.com,2011-05-01:/2011/05/01/new-project-calcsubnet/</id>
    <title type="html">new project - calcsub.net</title>
    <published>2011-04-30T22:00:00Z</published>
    <updated>2011-04-30T22:00:00Z</updated>
    <author>
      <name>Leif Gensert</name>
      <uri>http://www.grepthepipe.com</uri>
    </author>
    <link rel="alternate" href="http://grepthepipe.com/2011/05/01/new-project-calcsubnet/"/>
    <content type="html">&lt;p&gt;Over the easter holidays I started working on a new project. Today it has finally reached a state where I’m confident to say: I can go&amp;nbsp;public.&lt;/p&gt;

&lt;p&gt;It’s just a simple subnet calculator that takes IPv4 and IPv6 addresses and then calculates the start address and the end&amp;nbsp;address.&lt;/p&gt;

&lt;p&gt;You can have a look at it &lt;a href="http://calcsub.net"&gt;here&lt;/a&gt; or see the source on &lt;a href="https://github.com/leifg/calcsub.net"&gt;github&lt;/a&gt;.&lt;/p&gt;

&lt;p&gt;The project is also added to the &lt;a href="http://grepthepipe.com/portfolio.html"&gt;portfolio page&lt;/a&gt;.&lt;/p&gt;

&lt;div class="annotation"&gt;
  &lt;p&gt;picture created by Leif Gensert. &lt;a href="http://creativecommons.org/licenses/by/2.0/"&gt;&lt;span class="caps"&gt;CC&lt;/span&gt; &lt;span class="caps"&gt;BY&lt;/span&gt; &lt;span class="caps"&gt;2.0&lt;/span&gt;&lt;/a&gt;&amp;lt;/div&amp;gt;&lt;/p&gt;
&lt;/div&gt;
</content>
  </entry>
  <entry>
    <id>tag:grepthepipe.com,2011-04-30:/2011/04/30/sexy-tech-links-of-april/</id>
    <title type="html">sexy tech links of april (last one)</title>
    <published>2011-04-29T22:00:00Z</published>
    <updated>2011-04-29T22:00:00Z</updated>
    <author>
      <name>Leif Gensert</name>
      <uri>http://www.grepthepipe.com</uri>
    </author>
    <link rel="alternate" href="http://grepthepipe.com/2011/04/30/sexy-tech-links-of-april/"/>
    <content type="html">&lt;p&gt;Notice: this bit will be the last “tech links of #{month}”. I decided to focus more on regular articles in the&amp;nbsp;future.&lt;/p&gt;

&lt;ul&gt;
  &lt;li&gt;&lt;a href="http://cl.ly/5nAo"&gt;Which open source license? - flowchart&lt;/a&gt; - Just in case you want to publish&amp;nbsp;something.&lt;/li&gt;
  &lt;li&gt;&lt;a href="http://uxmovement.com/navigation/why-sign-up-and-sign-in-should-never-go-together"&gt;Why Sign Up and Sign In Should Never Go Together&lt;/a&gt; - I try to keep that in mind if i ever get to build a system which requires user&amp;nbsp;accounts.&lt;/li&gt;
  &lt;li&gt;&lt;a href="http://elankeeran.com/wp/2011/04/html5-page-structure/"&gt;&lt;span class="caps"&gt;HTML5&lt;/span&gt; Page Structure&lt;/a&gt; - Lots of new&amp;nbsp;metadata.&lt;/li&gt;
&lt;/ul&gt;
</content>
  </entry>
  <entry>
    <id>tag:grepthepipe.com,2011-03-31:/2011/03/31/sexy-tech-links-of-march/</id>
    <title type="html">sexy tech links of march</title>
    <published>2011-03-30T22:00:00Z</published>
    <updated>2011-03-30T22:00:00Z</updated>
    <author>
      <name>Leif Gensert</name>
      <uri>http://www.grepthepipe.com</uri>
    </author>
    <link rel="alternate" href="http://grepthepipe.com/2011/03/31/sexy-tech-links-of-march/"/>
    <content type="html">&lt;ul&gt;
  &lt;li&gt;&lt;a href="http://blog.movieos.org/post/3978784625"&gt;&lt;span class="caps"&gt;REST&lt;/span&gt;&lt;/a&gt; - &lt;span class="caps"&gt;REST&lt;/span&gt; is one of technologies, that nobody can explain. Here is a short overview where you can at least get an idea of what it might&amp;nbsp;be.&lt;/li&gt;
  &lt;li&gt;&lt;a href="http://javarevisited.blogspot.com/2011/03/10-find-command-in-unix-examples-basic.html"&gt;10 examples of using find command in &lt;span class="caps"&gt;UNIX&lt;/span&gt;&lt;/a&gt; - This kind of a selfish link. I’ll post it so that I can find it later. But you can use it as well&amp;nbsp;;-).&lt;/li&gt;
  &lt;li&gt;&lt;a href="http://jacquesmattheij.com/The+worst+program+I+ever+worked+on"&gt;The worst program I ever worked on&lt;/a&gt; - I think it will be a lot of fun to write code like&amp;nbsp;that.&lt;/li&gt;
&lt;/ul&gt;
</content>
  </entry>
</feed>
