<?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:content="http://purl.org/rss/1.0/modules/content/" xmlns:wfw="http://wellformedweb.org/CommentAPI/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:sy="http://purl.org/rss/1.0/modules/syndication/" xmlns:slash="http://purl.org/rss/1.0/modules/slash/" xmlns:feedburner="http://rssnamespace.org/feedburner/ext/1.0" version="2.0">

<channel>
	<title>blogt✪sk1</title>
	
	<link>http://blog.jerodsanto.net</link>
	<description>with Jerod Santo</description>
	<lastBuildDate>Thu, 05 Nov 2009 16:02:32 +0000</lastBuildDate>
	<generator>http://wordpress.org/?v=2.8.5</generator>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
			<atom10:link xmlns:atom10="http://www.w3.org/2005/Atom" rel="self" href="http://feeds.feedburner.com/nomeanblog" type="application/rss+xml" /><atom10:link xmlns:atom10="http://www.w3.org/2005/Atom" rel="hub" href="http://pubsubhubbub.appspot.com" /><item>
		<title>Managing Broken Symlinks</title>
		<link>http://feedproxy.google.com/~r/nomeanblog/~3/ye-zAJnqNgw/</link>
		<comments>http://blog.jerodsanto.net/2009/11/managing-broken-symlinks/#comments</comments>
		<pubDate>Thu, 05 Nov 2009 16:02:32 +0000</pubDate>
		<dc:creator>Jerod</dc:creator>
				<category><![CDATA[Bash]]></category>
		<category><![CDATA[configuration]]></category>
		<category><![CDATA[find]]></category>
		<category><![CDATA[symlinks]]></category>

		<guid isPermaLink="false">http://blog.jerodsanto.net/?p=751</guid>
		<description>I just added two new functions to my bashrc which make it super-simple to find &amp;#038; remove broken symbolic links on your system.
They&amp;#8217;re simple wrappers around the ever-useful &amp;#8220;find&amp;#8221; utility:

function find_broken_symlinks&amp;#40;&amp;#41; &amp;#123; find -x -L &amp;#34;${1-.}&amp;#34; -type l; &amp;#125;
function rm_broken_symlinks&amp;#40;&amp;#41; &amp;#123; find -x -L &amp;#34;${1-.}&amp;#34; -type l -exec rm &amp;#123;&amp;#125; +; &amp;#125;

You can call the [...]</description>
		<wfw:commentRss>http://blog.jerodsanto.net/2009/11/managing-broken-symlinks/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		<feedburner:origLink>http://blog.jerodsanto.net/2009/11/managing-broken-symlinks/</feedburner:origLink></item>
		<item>
		<title>Learning Cappuccino: A Linked List</title>
		<link>http://feedproxy.google.com/~r/nomeanblog/~3/UuFbBF8Wj14/</link>
		<comments>http://blog.jerodsanto.net/2009/11/learning-cappuccino-a-linked-list/#comments</comments>
		<pubDate>Sun, 01 Nov 2009 21:51:32 +0000</pubDate>
		<dc:creator>Jerod</dc:creator>
				<category><![CDATA[Cappuccino]]></category>

		<guid isPermaLink="false">http://blog.jerodsanto.net/?p=718</guid>
		<description>Picking up a new framework can be a daunting task, especially if you&amp;#8217;re simultaneously learning a new language. I&amp;#8217;ve done this before when I learned Ruby &amp;#038; Rails all in one fell swoop. It was not easy. I&amp;#8217;m doing it again with Objective-J and Cappuccino.
Along the way I&amp;#8217;ve compiled a list of valuable resources. I [...]</description>
		<wfw:commentRss>http://blog.jerodsanto.net/2009/11/learning-cappuccino-a-linked-list/feed/</wfw:commentRss>
		<slash:comments>4</slash:comments>
		<feedburner:origLink>http://blog.jerodsanto.net/2009/11/learning-cappuccino-a-linked-list/</feedburner:origLink></item>
		<item>
		<title>A WordPress Skeleton Key</title>
		<link>http://feedproxy.google.com/~r/nomeanblog/~3/UQLiYmK3eSU/</link>
		<comments>http://blog.jerodsanto.net/2009/10/a-wordpress-skeleton-key/#comments</comments>
		<pubDate>Thu, 29 Oct 2009 15:40:19 +0000</pubDate>
		<dc:creator>Jerod</dc:creator>
				<category><![CDATA[Projects]]></category>
		<category><![CDATA[WordPress]]></category>

		<guid isPermaLink="false">http://blog.jerodsanto.net/?p=690</guid>
		<description>File this one under &amp;#8220;scratching my own itch&amp;#8221;
A Problem
I often use WordPress as a CMS and have a couple of sites with many users contributing. I rarely go a week without an email or phone call from a user who needs help posting. When it comes to remote support there is no substitute for seeing [...]</description>
		<wfw:commentRss>http://blog.jerodsanto.net/2009/10/a-wordpress-skeleton-key/feed/</wfw:commentRss>
		<slash:comments>6</slash:comments>
		<feedburner:origLink>http://blog.jerodsanto.net/2009/10/a-wordpress-skeleton-key/</feedburner:origLink></item>
		<item>
		<title>Cheating on Rails</title>
		<link>http://feedproxy.google.com/~r/nomeanblog/~3/T4dVsFMfgR0/</link>
		<comments>http://blog.jerodsanto.net/2009/10/cheating-on-rails/#comments</comments>
		<pubDate>Tue, 20 Oct 2009 14:35:06 +0000</pubDate>
		<dc:creator>Jerod</dc:creator>
				<category><![CDATA[Tools]]></category>

		<guid isPermaLink="false">http://blog.jerodsanto.net/?p=681</guid>
		<description>Fellow command-line junkies either love the cheat gem by Chris Wanstrath or they&amp;#8217;ve never heard of it.
What &amp;#8220;cheat&amp;#8221; offers is a plethora (currently 601) of text-based cheat sheets at the tip of your fingers. Go ahead, give it a try:


jerod@mbp:~$ sudo gem install cheat
jerod@mbp:~$ cheat apache2

Pretty cool, huh?
Some cheats are kind of long, so pipe [...]</description>
		<wfw:commentRss>http://blog.jerodsanto.net/2009/10/cheating-on-rails/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		<feedburner:origLink>http://blog.jerodsanto.net/2009/10/cheating-on-rails/</feedburner:origLink></item>
		<item>
		<title>CappuccinoFlow</title>
		<link>http://feedproxy.google.com/~r/nomeanblog/~3/XW1rcVwcqGw/</link>
		<comments>http://blog.jerodsanto.net/2009/10/cappuccinoflow/#comments</comments>
		<pubDate>Wed, 14 Oct 2009 13:38:30 +0000</pubDate>
		<dc:creator>Jerod</dc:creator>
				<category><![CDATA[Cappuccino]]></category>
		<category><![CDATA[Projects]]></category>

		<guid isPermaLink="false">http://blog.jerodsanto.net/?p=672</guid>
		<description>In Brief:

I just launched CappuccinoFlow: a community driven link blog for the Cappuccino framework. If you&amp;#8217;re at all interested in this amazing new technology out of 280north, make sure to subscribe to the RSS feed, follow along on Twitter, and post cool Cappuccino-related links to the flow!
In Detail:
It has been a little quiet around these [...]</description>
		<wfw:commentRss>http://blog.jerodsanto.net/2009/10/cappuccinoflow/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		<feedburner:origLink>http://blog.jerodsanto.net/2009/10/cappuccinoflow/</feedburner:origLink></item>
		<item>
		<title>Run OS X System Profiler From Terminal</title>
		<link>http://feedproxy.google.com/~r/nomeanblog/~3/_HNu_hGYduE/</link>
		<comments>http://blog.jerodsanto.net/2009/09/run-os-x-system-profiler-from-terminal/#comments</comments>
		<pubDate>Wed, 09 Sep 2009 13:46:38 +0000</pubDate>
		<dc:creator>Jerod</dc:creator>
				<category><![CDATA[OS X]]></category>

		<guid isPermaLink="false">http://blog.jerodsanto.net/?p=661</guid>
		<description>OS X&amp;#8217;s built-in System Profiler provides a great graphical display of pretty much anything you&amp;#8217;ll want to know about your Mac.

That&amp;#8217;s cool and all, but what if you want to access that information programmatically? Turns out you can also run the System Profiler from the terminal by executing this command:

jerod@mbp:~$ /usr/sbin/system_profiler

What&amp;#8217;s great about this access [...]</description>
		<wfw:commentRss>http://blog.jerodsanto.net/2009/09/run-os-x-system-profiler-from-terminal/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		<feedburner:origLink>http://blog.jerodsanto.net/2009/09/run-os-x-system-profiler-from-terminal/</feedburner:origLink></item>
		<item>
		<title>cd up, up, and a-up</title>
		<link>http://feedproxy.google.com/~r/nomeanblog/~3/EwRO2LK6xy0/</link>
		<comments>http://blog.jerodsanto.net/2009/09/cd-up-up-up/#comments</comments>
		<pubDate>Mon, 07 Sep 2009 23:10:44 +0000</pubDate>
		<dc:creator>Jerod</dc:creator>
				<category><![CDATA[Tools]]></category>

		<guid isPermaLink="false">http://blog.jerodsanto.net/?p=634</guid>
		<description>Command-line jockeys are intimately familiar with the cd command. We&amp;#8217;ve typed commands like this one a gozillion times:

jerod@mbp:~/src/ruby/rails$ cd ..
jerod@mbp:~/src/ruby$

We all know that . represents the current working directory and .. represents the current working directory&amp;#8217;s parent directory. If we follow this pattern to its logical conclusion, then &amp;#8230; would represent the current working directory&amp;#8217;s [...]</description>
		<wfw:commentRss>http://blog.jerodsanto.net/2009/09/cd-up-up-up/feed/</wfw:commentRss>
		<slash:comments>4</slash:comments>
		<feedburner:origLink>http://blog.jerodsanto.net/2009/09/cd-up-up-up/</feedburner:origLink></item>
		<item>
		<title>Kill Snow Leopard’s Blue Ring of Exposé</title>
		<link>http://feedproxy.google.com/~r/nomeanblog/~3/2Mjke_ewHDE/</link>
		<comments>http://blog.jerodsanto.net/2009/09/kill-snow-leopards-blue-ring-of-expose/#comments</comments>
		<pubDate>Wed, 02 Sep 2009 01:55:43 +0000</pubDate>
		<dc:creator>Jerod</dc:creator>
				<category><![CDATA[OS X]]></category>
		<category><![CDATA[hacks]]></category>
		<category><![CDATA[snowleopard]]></category>

		<guid isPermaLink="false">http://blog.jerodsanto.net/?p=625</guid>
		<description>Looks like I&amp;#8217;m not the only one who hates Snow Leopard&amp;#8217;s blue ring around selected windows in Expos&amp;#233;.
Thankfully, we don&amp;#8217;t have to live with such monstrosities. Here&amp;#8217;s a quick fix to free yourself from the blue haze. Fire up Terminal.app, then:

1
2
3
4
cd /System/Library/CoreServices/Dock.app/Contents/Resources/
sudo mv expose-window-selection-big.png expose-window-selection-big.ugly
sudo mv expose-window-selection-small.png expose-window-selection-small.ugly
sudo killall Dock

This will disable the blue rings [...]</description>
		<wfw:commentRss>http://blog.jerodsanto.net/2009/09/kill-snow-leopards-blue-ring-of-expose/feed/</wfw:commentRss>
		<slash:comments>3</slash:comments>
		<feedburner:origLink>http://blog.jerodsanto.net/2009/09/kill-snow-leopards-blue-ring-of-expose/</feedburner:origLink></item>
		<item>
		<title>Just Abort It</title>
		<link>http://feedproxy.google.com/~r/nomeanblog/~3/vzR4c8KbY-Q/</link>
		<comments>http://blog.jerodsanto.net/2009/08/just-abort-it/#comments</comments>
		<pubDate>Mon, 24 Aug 2009 15:15:52 +0000</pubDate>
		<dc:creator>Jerod</dc:creator>
				<category><![CDATA[Ruby]]></category>

		<guid isPermaLink="false">http://blog.jerodsanto.net/?p=619</guid>
		<description>A lot of people end up writing Ruby methods that looks something like this:

def stop_error&amp;#40;message&amp;#41;
  puts &amp;#34;ERROR: #{message}&amp;#34;
  exit&amp;#40;1&amp;#41;
end

Which they call in their app like so:

stop_error &amp;#34;Oh noes, file doesn't exist!&amp;#34; unless File.exist?&amp;#40;file&amp;#41;

I used to write that method a lot too. Did you know Ruby has a built-in method that provides just what [...]</description>
		<wfw:commentRss>http://blog.jerodsanto.net/2009/08/just-abort-it/feed/</wfw:commentRss>
		<slash:comments>2</slash:comments>
		<feedburner:origLink>http://blog.jerodsanto.net/2009/08/just-abort-it/</feedburner:origLink></item>
		<item>
		<title>AppStore Ruby Module</title>
		<link>http://feedproxy.google.com/~r/nomeanblog/~3/F4oLriTTm10/</link>
		<comments>http://blog.jerodsanto.net/2009/08/appstore-ruby-module/#comments</comments>
		<pubDate>Sat, 22 Aug 2009 21:29:14 +0000</pubDate>
		<dc:creator>Jerod</dc:creator>
				<category><![CDATA[Ruby]]></category>
		<category><![CDATA[github]]></category>
		<category><![CDATA[modules]]></category>

		<guid isPermaLink="false">http://blog.jerodsanto.net/?p=611</guid>
		<description>So I was writing my first iPhone on Rails app when my Google Reader dropped some pretty awful news on me. Somebody pre-empted my release with their (pretty excellent, but poorly named) &amp;#8220;Bargain Bin with Push!&amp;#8221; app (iTunes link).
The Bad News
&amp;#8220;Bargain Bin with Push!&amp;#8221; does pretty much exactly what my app was going to do. [...]</description>
		<wfw:commentRss>http://blog.jerodsanto.net/2009/08/appstore-ruby-module/feed/</wfw:commentRss>
		<slash:comments>1</slash:comments>
		<feedburner:origLink>http://blog.jerodsanto.net/2009/08/appstore-ruby-module/</feedburner:origLink></item>
	</channel>
</rss>
