<?xml version="1.0" encoding="UTF-8"?>
<?xml-stylesheet type="text/xsl" media="screen" href="/~d/styles/rss2full.xsl"?><?xml-stylesheet type="text/css" media="screen" href="http://feeds.feedburner.com/~d/styles/itemcontent.css"?><rss xmlns:atom="http://www.w3.org/2005/Atom" xmlns:feedburner="http://rssnamespace.org/feedburner/ext/1.0" version="2.0"> 
    <channel>
        <title>SymKat - Bloggity Blog</title>
        <link>http://www.symkat.com/index.xml</link>
        
        <description>The RSS 2.0 Feed for SymKat</description>
        <language>en-us</language>
        <generator>SymKat RSS Generator 1.0</generator>
        <webMaster>symkat@symkat.com (SymKat)</webMaster>
                    <atom10:link xmlns:atom10="http://www.w3.org/2005/Atom" rel="self" type="application/rss+xml" href="http://feeds.feedburner.com/SymKat" /><feedburner:info uri="symkat" /><atom10:link xmlns:atom10="http://www.w3.org/2005/Atom" rel="hub" href="http://pubsubhubbub.appspot.com/" /><item>
                <title>Credential Management in DBIx::Class</title>
                <link>http://feedproxy.google.com/~r/SymKat/~3/NBtkYty5-js/credential-management-in-dbix-class</link>
                <pubDate>Tue, 04 Oct 2011 18:11:59 PST</pubDate>
                <description>&lt;p&gt;Posted in &lt;a href="http://www.symkat.com/category/code"&gt;Code&lt;/a&gt;&lt;/p&gt;
                &lt;p&gt;Most companies have a method of storing passwords and configuration details in a configuration file.  For programmers working on on DBIx::Class, this usually means writing your own functions to load a configuration file and supplying them to &lt;code&gt;-&amp;gt;connect()&lt;/code&gt;.  If you're working on something like a web framework, chances are you're writing something similar like Dancer's Plugin::DBIC or Catalyst's Model::DBIC::Schema.&lt;/p&gt;

&lt;p&gt;DBIx::Class::Schema::Config can be added to any DBIC Schema to allow it to connect to a database with pre-configured credentials in any format that Config::Any recognizes, takes one additional line of code in a schema file, one change to your &lt;code&gt;-&amp;gt;connect()&lt;/code&gt; statement, and takes less than a minute to configure after it's been installed&lt;/p&gt;&lt;img src="http://feeds.feedburner.com/~r/SymKat/~4/NBtkYty5-js" height="1" width="1"/&gt;</description>
                <guid isPermaLink="false">http://www.symkat.com/credential-management-in-dbix-class</guid>
            <feedburner:origLink>http://www.symkat.com/credential-management-in-dbix-class</feedburner:origLink></item>
                    <item>
                <title>Find a Perl Module's Path</title>
                <link>http://feedproxy.google.com/~r/SymKat/~3/RoFqoOqEG5o/find-a-perl-modules-path</link>
                <pubDate>Wed, 27 Oct 2010 06:00:00 PST</pubDate>
                <description>&lt;p&gt;Posted in &lt;a href="http://www.symkat.com/category/programming"&gt;Programming&lt;/a&gt;&lt;/p&gt;
                &lt;p&gt;Not every module is created perfectly and you may want to review the code you're loading into your project, identify bugs or generally poke around.&lt;/p&gt;

&lt;p&gt;While multiple versions of a given module may be installed, finding the version you're using is rather simple if you let Perl itself tell you.&lt;/p&gt;&lt;img src="http://feeds.feedburner.com/~r/SymKat/~4/RoFqoOqEG5o" height="1" width="1"/&gt;</description>
                <guid isPermaLink="false">http://www.symkat.com/find-a-perl-modules-path</guid>
            <feedburner:origLink>http://www.symkat.com/find-a-perl-modules-path</feedburner:origLink></item>
                    <item>
                <title>Force Download with HTTP Headers</title>
                <link>http://feedproxy.google.com/~r/SymKat/~3/x3WEFaZq6wA/force-download-with-http-headers</link>
                <pubDate>Wed, 20 Oct 2010 06:00:00 PST</pubDate>
                <description>&lt;p&gt;Posted in &lt;a href="http://www.symkat.com/category/http"&gt;HTTP&lt;/a&gt;&lt;/p&gt;
                &lt;p&gt;Modern web browsers support a plethora of plugins to allow content to be displayed inline; once upon a time your mp3 and pdf files would prompt a download box, now more-often than not they are displayed inside the browser.&lt;/p&gt;

&lt;p&gt;While no one is arguing that the advancements of inline content displayed in web browsers are not without merit (okay, maybe you can tone down some of the flash...), a webmaster may occasionally wish to force a download box to pop up for one reason or another.&lt;/p&gt;&lt;img src="http://feeds.feedburner.com/~r/SymKat/~4/x3WEFaZq6wA" height="1" width="1"/&gt;</description>
                <guid isPermaLink="false">http://www.symkat.com/force-download-with-http-headers</guid>
            <feedburner:origLink>http://www.symkat.com/force-download-with-http-headers</feedburner:origLink></item>
                    <item>
                <title>Stalker - Nickname History For IRSSI </title>
                <link>http://feedproxy.google.com/~r/SymKat/~3/IbymhIIIvLU/stalker</link>
                <pubDate>Wed, 06 Oct 2010 06:00:00 PST</pubDate>
                <description>&lt;p&gt;Posted in &lt;a href="http://www.symkat.com/category/code"&gt;Code&lt;/a&gt;&lt;/p&gt;
                &lt;p&gt;Stalker is an irssi plugin to correlate information on an IRC network and discover users' previously used nicknames.  The concept is fairly straightforward: given a nickname identify previously used hostnames.  From those hostnames, extract all nicknames they have used.  Repeat until you have identified all nicknames a user might have used.  The advantage of this method over the more traditional &lt;em&gt;given a hostname identify all nicknames it has used&lt;/em&gt; is that you can identify nicknames across hostmask addresses.&lt;/p&gt;&lt;img src="http://feeds.feedburner.com/~r/SymKat/~4/IbymhIIIvLU" height="1" width="1"/&gt;</description>
                <guid isPermaLink="false">http://www.symkat.com/stalker</guid>
            <feedburner:origLink>http://www.symkat.com/stalker</feedburner:origLink></item>
                    <item>
                <title>Introducing SymPullCDN</title>
                <link>http://feedproxy.google.com/~r/SymKat/~3/iF7w7pKM5uc/sympull-cdn</link>
                <pubDate>Wed, 29 Sep 2010 06:00:00 PST</pubDate>
                <description>&lt;p&gt;Posted in &lt;a href="http://www.symkat.com/category/code"&gt;Code&lt;/a&gt;&lt;/p&gt;
                &lt;p&gt;&lt;a href="SymPullCDN"&gt;SymPullCDN&lt;/a&gt; leverages the free bandwidth, storage and power of Google &lt;a href="AppEngine"&gt;AppEngine&lt;/a&gt; to create a trivial to implement reverse proxy.  It has been released to the public for free on github.&lt;/p&gt;&lt;img src="http://feeds.feedburner.com/~r/SymKat/~4/iF7w7pKM5uc" height="1" width="1"/&gt;</description>
                <guid isPermaLink="false">http://www.symkat.com/sympull-cdn</guid>
            <feedburner:origLink>http://www.symkat.com/sympull-cdn</feedburner:origLink></item>
                    <item>
                <title>Cookieless Domains</title>
                <link>http://feedproxy.google.com/~r/SymKat/~3/haKEv5KqP04/cookieless-domains</link>
                <pubDate>Tue, 21 Sep 2010 06:00:00 PST</pubDate>
                <description>&lt;p&gt;Posted in &lt;a href="http://www.symkat.com/category/http"&gt;HTTP&lt;/a&gt;&lt;/p&gt;
                &lt;p&gt;The premise of cookieless domains is that one can speed up an HTTP transaction and the amount of entities downloaded at the same time to increase the rendering time of a page.  This seems perfectly rational when we take a look at the logic behind it.  We'll take a look at if this actually &lt;em&gt;does&lt;/em&gt; speed up your website.&lt;/p&gt;&lt;img src="http://feeds.feedburner.com/~r/SymKat/~4/haKEv5KqP04" height="1" width="1"/&gt;</description>
                <guid isPermaLink="false">http://www.symkat.com/cookieless-domains</guid>
            <feedburner:origLink>http://www.symkat.com/cookieless-domains</feedburner:origLink></item>
                    <item>
                <title>Understanding Bash History</title>
                <link>http://feedproxy.google.com/~r/SymKat/~3/176IRy7kVD4/understanding-bash-history</link>
                <pubDate>Wed, 15 Sep 2010 06:00:00 PST</pubDate>
                <description>&lt;p&gt;Posted in &lt;a href="http://www.symkat.com/category/systems-administration"&gt;Systems Administration&lt;/a&gt;&lt;/p&gt;
                &lt;p&gt;Understanding how to fully utilize bash's history functions are paramount to being able to quickly recall commands and navigate the terminal.
This article focuses on the lesser-known commands built into &lt;code&gt;bash&lt;/code&gt; for speed of recalling previous commands.&lt;/p&gt;&lt;img src="http://feeds.feedburner.com/~r/SymKat/~4/176IRy7kVD4" height="1" width="1"/&gt;</description>
                <guid isPermaLink="false">http://www.symkat.com/understanding-bash-history</guid>
            <feedburner:origLink>http://www.symkat.com/understanding-bash-history</feedburner:origLink></item>
                    <item>
                <title>Stop Lying On Your Resume</title>
                <link>http://feedproxy.google.com/~r/SymKat/~3/ldOcKb5eYYE/stop-lying-on-your-resume</link>
                <pubDate>Wed, 08 Sep 2010 06:00:00 PST</pubDate>
                <description>&lt;p&gt;Posted in &lt;a href="http://www.symkat.com/category/thoughts"&gt;Thoughts&lt;/a&gt;&lt;/p&gt;
                &lt;p&gt;Believe it or not, most interviews aren't actually about finding out if you're good at what you do or not.  They're mostly about finding out if you're a good person.&lt;/p&gt;

&lt;p&gt;Lying on your resume can make this process go very badly when you meet The Technical Interviewer.&lt;/p&gt;&lt;img src="http://feeds.feedburner.com/~r/SymKat/~4/ldOcKb5eYYE" height="1" width="1"/&gt;</description>
                <guid isPermaLink="false">http://www.symkat.com/stop-lying-on-your-resume</guid>
            <feedburner:origLink>http://www.symkat.com/stop-lying-on-your-resume</feedburner:origLink></item>
                    <item>
                <title>Understanding Job Control In Bash</title>
                <link>http://feedproxy.google.com/~r/SymKat/~3/1NGWuhz9U0E/understanding-job-control-in-bash</link>
                <pubDate>Wed, 01 Sep 2010 06:00:00 PST</pubDate>
                <description>&lt;p&gt;Posted in &lt;a href="http://www.symkat.com/category/systems-administration"&gt;Systems Administration&lt;/a&gt;&lt;/p&gt;
                &lt;p&gt;Between opening a number of shells and running a screen multiplexer like &lt;code&gt;screen&lt;/code&gt; there are many ways people utilize terminals to run multiple commands at once.  Bash provides its own built-in way of handling this: Job Control.&lt;/p&gt;

&lt;p&gt;Each process being executed is a child process of the bash shell.  Job Control allows you to attach and detach from the child processes.&lt;/p&gt;&lt;img src="http://feeds.feedburner.com/~r/SymKat/~4/1NGWuhz9U0E" height="1" width="1"/&gt;</description>
                <guid isPermaLink="false">http://www.symkat.com/understanding-job-control-in-bash</guid>
            <feedburner:origLink>http://www.symkat.com/understanding-job-control-in-bash</feedburner:origLink></item>
                    <item>
                <title>Understanding File Descriptors and IO Redirection</title>
                <link>http://feedproxy.google.com/~r/SymKat/~3/ptnQO0EedDQ/understanding-file-descriptors-and-io-redirection</link>
                <pubDate>Wed, 25 Aug 2010 06:00:00 PST</pubDate>
                <description>&lt;p&gt;Posted in &lt;a href="http://www.symkat.com/category/programming"&gt;Programming&lt;/a&gt;&lt;/p&gt;
                &lt;p&gt;The ability to string together data between processes and controlling where it comes from and goes to is ultimately a very large aspect of what makes Linux and Unix systems great.  In this article we will take a look at the methods for doing so as well as describe where this data is coming from and going.  A solid understanding of redirection and file descriptors is mandatory for any systems administrator or programmer working with a UNIX-like system.&lt;/p&gt;&lt;img src="http://feeds.feedburner.com/~r/SymKat/~4/ptnQO0EedDQ" height="1" width="1"/&gt;</description>
                <guid isPermaLink="false">http://www.symkat.com/understanding-file-descriptors-and-io-redirection</guid>
            <feedburner:origLink>http://www.symkat.com/understanding-file-descriptors-and-io-redirection</feedburner:origLink></item>
            </channel>
</rss>
