<?xml version="1.0" encoding="utf-8"?>
<feed xmlns="http://www.w3.org/2005/Atom">
    <title>Jerome Eteve</title>
    <link rel="alternate" type="text/html" href="http://blogs.perl.org/users/jerome_eteve/" />
    <link rel="self" type="application/atom+xml" href="http://blogs.perl.org/users/jerome_eteve/atom.xml" />
    <id>tag:blogs.perl.org,2009-11-03:/users/jerome_eteve//638</id>
    <updated>2013-03-13T17:35:58Z</updated>
    <subtitle>A blog about the Perl programming language</subtitle>
    <generator uri="http://www.sixapart.com/movabletype/">Movable Type Pro 4.38</generator>

<entry>
    <title>Mason - A Template system for us programmers</title>
    <link rel="alternate" type="text/html" href="http://blogs.perl.org/users/jerome_eteve/2013/03/mason---a-template-system-for-us-programmers.html" />
    <id>tag:blogs.perl.org,2013:/users/jerome_eteve//638.4427</id>

    <published>2013-03-13T17:24:07Z</published>
    <updated>2013-03-13T17:35:58Z</updated>

    <summary>Templating Modules are a bit like editors. Every web application developer has a favourite one. And every template system is someone&apos;s favorite. Mine is Mason. But not because the Perl MVC tutorials are full of examples using Mason. Not because...</summary>
    <author>
        <name>Jerome Eteve</name>
        <uri>http://www.eteve.net</uri>
    </author>
    
    
    <content type="html" xml:lang="en" xml:base="http://blogs.perl.org/users/jerome_eteve/">
        <![CDATA[<p>Templating Modules are a bit like editors. Every web application developer has a favourite one. And every template system is someone's favorite.</p>

<p>Mine is Mason. But not because the Perl MVC tutorials are full of examples using Mason. Not because it's the fastest (use xSlate if you want to trade speed for flexibility). Not because it's the most popular. It's my favourite for a very plain reason: It makes me more productive and allows me to develop web GUIs using all the powerful features a programmer should biterly miss if they are taken away. That includes writing Perl code :P</p>

<p>I never heard of a business that went down because they didn't have fast enough CPUs, so I'm not fussy about trading a few CPU cycles for elegance, ease and speed of development.</p>

<p>Enough talking. <a href="http://sigstp.blogspot.co.uk/2013/03/mason-template-system-for-us-programmers.html">Here's my contribution to the template holy war</a>.</p>]]>
        
    </content>
</entry>

<entry>
    <title> The only bad thing about Mason </title>
    <link rel="alternate" type="text/html" href="http://blogs.perl.org/users/jerome_eteve/2013/03/the-only-bad-thing-about-mason.html" />
    <id>tag:blogs.perl.org,2013:/users/jerome_eteve//638.4388</id>

    <published>2013-03-02T20:06:39Z</published>
    <updated>2013-03-02T20:08:16Z</updated>

    <summary>At the moment, I&apos;m writing a presentation about Mason2. The goal is to somehow convince my colleagues to consider using Mason. Instead of Template Toolkit. As part of it, I thought I&apos;d do a bit of performance benchmarking against Template...</summary>
    <author>
        <name>Jerome Eteve</name>
        <uri>http://www.eteve.net</uri>
    </author>
    
    <category term="benchmarking" label="benchmarking" scheme="http://www.sixapart.com/ns/types#tag" />
    <category term="mason" label="mason" scheme="http://www.sixapart.com/ns/types#tag" />
    
    <content type="html" xml:lang="en" xml:base="http://blogs.perl.org/users/jerome_eteve/">
        <![CDATA[<p>At the moment, I'm writing a presentation about Mason2. The goal is to somehow convince my colleagues to consider using Mason. Instead of Template Toolkit.<br />
As part of it, I thought I'd do a bit of performance benchmarking against Template Toolkit. So I put together a reasonably complex mini set of templates using both systems. Well, as complex as TT can take in reality. Which is not very much.</p>

<p><a href="http://sigstp.blogspot.co.uk/2013/03/the-only-bad-thing-about-mason.html">But anyway, let's jump straight to the bad news.</a></p>]]>
        
    </content>
</entry>

<entry>
    <title>Give your application a shell (and never write any ad-hoc scripts again)</title>
    <link rel="alternate" type="text/html" href="http://blogs.perl.org/users/jerome_eteve/2013/02/give-your-application-a-shell-and-never-write-any-ad-hoc-scripts-again.html" />
    <id>tag:blogs.perl.org,2013:/users/jerome_eteve//638.4362</id>

    <published>2013-02-21T14:07:39Z</published>
    <updated>2013-02-21T14:08:44Z</updated>

    <summary>As developers, we sometimes have to help operations going smoothly by fiddling with the data &quot;by hand&quot; because there&apos;s no GUI to allow people doing some rare and obscure things. One common way of doing it is by connecting to...</summary>
    <author>
        <name>Jerome Eteve</name>
        <uri>http://www.eteve.net</uri>
    </author>
    
    <category term="cli" label="cli" scheme="http://www.sixapart.com/ns/types#tag" />
    <category term="development" label="development" scheme="http://www.sixapart.com/ns/types#tag" />
    
    <content type="html" xml:lang="en" xml:base="http://blogs.perl.org/users/jerome_eteve/">
        <![CDATA[<p>As developers, we sometimes have to help operations going smoothly by fiddling with the data "by hand" because there's no GUI to allow people doing some rare and obscure things. One common way of doing it is by connecting to the DB and writing some SQL. But often, accessing your database is not enough, because you need your application code to be run.</p>

<p><a href="http://sigstp.blogspot.co.uk/2013/02/give-your-application-shell-and-never.html">And for that, you need a shell.</a></p>]]>
        
    </content>
</entry>

<entry>
    <title>Friday Time Waster: Watch the world go by in ASCII with Reuters&apos; API</title>
    <link rel="alternate" type="text/html" href="http://blogs.perl.org/users/jerome_eteve/2012/11/friday-time-waster-watch-the-world-go-by-in-ascii-with-reuters-api.html" />
    <id>tag:blogs.perl.org,2012:/users/jerome_eteve//638.4063</id>

    <published>2012-11-23T14:09:43Z</published>
    <updated>2012-11-23T14:11:52Z</updated>

    <summary>I&apos;ve recently released WebService::ReutersConnect. It&apos;s a Perl modules that interfaces with the ReutersConnect&apos;s API in OO style. To demonstrate it and hopefully entertain you on this Friday, here&apos;s how to use it to watch the world go by in glorious...</summary>
    <author>
        <name>Jerome Eteve</name>
        <uri>http://www.eteve.net</uri>
    </author>
    
    <category term="ascii" label="ascii" scheme="http://www.sixapart.com/ns/types#tag" />
    <category term="development" label="development" scheme="http://www.sixapart.com/ns/types#tag" />
    <category term="news" label="news" scheme="http://www.sixapart.com/ns/types#tag" />
    
    <content type="html" xml:lang="en" xml:base="http://blogs.perl.org/users/jerome_eteve/">
        <![CDATA[<p>I've recently released <a href="http://search.cpan.org/perldoc?WebService%3A%3AReutersConnect">WebService::ReutersConnect</a>. It's a Perl modules that interfaces with the ReutersConnect's API in OO style. To demonstrate it and hopefully entertain you on this Friday, here's how to use it to watch the world go by in glorious ASCII and from the comfort of your command line. To put it shorter: The perfect Friday Time Waster.</p>

<p><a href="http://sigstp.blogspot.co.uk/2012/11/friday-time-waster-watch-world-go-by-in.html">Read more here.</a></p>

<p></p>

<p><br />
</p>]]>
        
    </content>
</entry>

<entry>
    <title>Understanding Unicode/UTF8 in Perl</title>
    <link rel="alternate" type="text/html" href="http://blogs.perl.org/users/jerome_eteve/2012/09/understanding-unicodeutf8-in-perl.html" />
    <id>tag:blogs.perl.org,2012:/users/jerome_eteve//638.3888</id>

    <published>2012-09-26T09:26:30Z</published>
    <updated>2012-09-26T10:45:46Z</updated>

    <summary>I&apos;m not a Unicode Guru, but working with third parties, I often find that a lot of people consistently fail to get the basics right about Unicode and encoding. So here&apos;s yet another set of slides about unicode/utf8 in Perl....</summary>
    <author>
        <name>Jerome Eteve</name>
        <uri>http://www.eteve.net</uri>
    </author>
    
    <category term="development" label="development" scheme="http://www.sixapart.com/ns/types#tag" />
    <category term="unicode" label="unicode" scheme="http://www.sixapart.com/ns/types#tag" />
    
    <content type="html" xml:lang="en" xml:base="http://blogs.perl.org/users/jerome_eteve/">
        <![CDATA[<p>I'm not a Unicode Guru, but working with third parties, I often find that a lot of people consistently fail to get the basics right about Unicode and encoding. So here's yet another set of slides about unicode/utf8 in Perl.</p>

<p> It's not meant to be a comprehensive presentation of all Unicode things in Perl. It's meant to insist on a couple of guidelines and give some pointers to get a good start writing a unicode compliant application and avoiding common issues.</p>

<p><a href="http://sigstp.blogspot.co.uk/2012/09/understanding-unicode-and-utf8-in-perl.html">View them here.</a></p>

<p><br />
</p>]]>
        
    </content>
</entry>

<entry>
    <title>The goodness of testing</title>
    <link rel="alternate" type="text/html" href="http://blogs.perl.org/users/jerome_eteve/2012/08/the-goodness-of-testing.html" />
    <id>tag:blogs.perl.org,2012:/users/jerome_eteve//638.3721</id>

    <published>2012-08-22T09:22:03Z</published>
    <updated>2012-08-22T09:28:27Z</updated>

    <summary>This is not strictly related to Perl, but I was thinking about my practice of testing recently and I&apos;ve come to some conclusions, some of them proving to be a bit controversial. Read more here and have your say!...</summary>
    <author>
        <name>Jerome Eteve</name>
        <uri>http://www.eteve.net</uri>
    </author>
    
    <category term="development" label="development" scheme="http://www.sixapart.com/ns/types#tag" />
    <category term="testing" label="testing" scheme="http://www.sixapart.com/ns/types#tag" />
    
    <content type="html" xml:lang="en" xml:base="http://blogs.perl.org/users/jerome_eteve/">
        <![CDATA[<p>This is not strictly related to Perl, but I was thinking about my practice of testing recently and I've come to some conclusions, some of them proving to be a bit controversial. <a href="http://sigstp.blogspot.co.uk/2012/08/the-goodness-of-testing.html">Read more here</a> and have your say!</p>]]>
        
    </content>
</entry>

</feed>
