<?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"?><!-- generator="WordPress/2.7.1" --><rss xmlns:feedburner="http://rssnamespace.org/feedburner/ext/1.0" version="0.92">
<channel>
	<title>labria's ruby blog</title>
	<link>http://blog.startika.com</link>
	<description>random ruby/rails stuff</description>
	<lastBuildDate>Sun, 20 Jun 2010 10:08:49 +0000</lastBuildDate>
	<docs>http://backend.userland.com/rss092</docs>
	<language>en</language>
	
	<atom10:link xmlns:atom10="http://www.w3.org/2005/Atom" rel="self" type="application/xml" href="http://feeds.feedburner.com/LabriasRubyBlog" /><feedburner:info uri="labriasrubyblog" /><atom10:link xmlns:atom10="http://www.w3.org/2005/Atom" rel="hub" href="http://pubsubhubbub.appspot.com/" /><item>
		<title>erlgen deprecated.</title>
		<description>I created my erlgen tool because I lacked something to do the job. Now i'm deprecating it, because such a tool was written.
Welcome Rebar! It's not simpy a generator, but a swiss knife for the complete erlang application lifecycle. Generation, dependencies, building, dialyzer, eunit, release, you name it — Rebar ...&lt;img src="http://feeds.feedburner.com/~r/LabriasRubyBlog/~4/er-yKelfS0k" height="1" width="1"/&gt;</description>
		<link>http://feedproxy.google.com/~r/LabriasRubyBlog/~3/er-yKelfS0k/</link>
			<feedburner:origLink>http://blog.startika.com/2010/06/20/erlgen-deprecated/</feedburner:origLink></item>
	<item>
		<title>Erlang application generator</title>
		<description>In the ruby world, we're used to code generators. Take rails, or the jeweler gem. When we start a project, we rarely start it from scratch, usually we have a skeleton to start with.
In the hardcore Erlang world, it's different. I found only one erlang project generator, the one bundled ...&lt;img src="http://feeds.feedburner.com/~r/LabriasRubyBlog/~4/pvecTp8BD4U" height="1" width="1"/&gt;</description>
		<link>http://feedproxy.google.com/~r/LabriasRubyBlog/~3/pvecTp8BD4U/</link>
			<feedburner:origLink>http://blog.startika.com/2010/04/01/erlang-application-generator/</feedburner:origLink></item>
	<item>
		<title>Naglfar release</title>
		<description>I finally found time in my schedule to release the Naglfar project. I've been thinking for a long time of a project to use the beautiful name, and I suddenly realized that the name itself is quite enough for me =)
To install, just do the usual:
gem install naglfar
The gem does ...&lt;img src="http://feeds.feedburner.com/~r/LabriasRubyBlog/~4/-nzXYIPqNJI" height="1" width="1"/&gt;</description>
		<link>http://feedproxy.google.com/~r/LabriasRubyBlog/~3/-nzXYIPqNJI/</link>
			<feedburner:origLink>http://blog.startika.com/2010/02/21/naglfar-release/</feedburner:origLink></item>
	<item>
		<title>My first working Erlang code.</title>
		<description>I wrote my first working bit of Erlang code. Wasn't much code, actually. Here it is:

out(A) -&gt;
    {ok, Challenge} = queryvar(A,"hub.challenge"),
    {html,io_lib:format('~s', [Challenge])}.

Wow... my highlighter doesn't even support Erlang! now it does
This a complete and finished piece of code, yes. If you heard of ...&lt;img src="http://feeds.feedburner.com/~r/LabriasRubyBlog/~4/prVU7LZcJ4Y" height="1" width="1"/&gt;</description>
		<link>http://feedproxy.google.com/~r/LabriasRubyBlog/~3/prVU7LZcJ4Y/</link>
			<feedburner:origLink>http://blog.startika.com/2009/09/15/my-first-erlang-code/</feedburner:origLink></item>
	<item>
		<title>A wonderful way to list your project files</title>
		<description>This article is published as a reply to the last few articles on the thoughtbot blog.
Some time or another during the project development you may wonder: «What files does my project include?» or «Why am I a Star Wars fan anyway?». This article will focus on the first question, leaving ...&lt;img src="http://feeds.feedburner.com/~r/LabriasRubyBlog/~4/cltYQV2UXOE" height="1" width="1"/&gt;</description>
		<link>http://feedproxy.google.com/~r/LabriasRubyBlog/~3/cltYQV2UXOE/</link>
			<feedburner:origLink>http://blog.startika.com/2009/09/10/a-wonderful-way-to-list-your-project-files/</feedburner:origLink></item>
	<item>
		<title>Freckle API.</title>
		<description>UPD: Freckle updated the API and docs. The new ones are here. 

I'm a Freckle user, and I love the service. The only thing I really miss is a simple client to store my time entries without visiting the site.
So, I sat down to write that simple client app, knowing ...&lt;img src="http://feeds.feedburner.com/~r/LabriasRubyBlog/~4/sE9gd_D9c5c" height="1" width="1"/&gt;</description>
		<link>http://feedproxy.google.com/~r/LabriasRubyBlog/~3/sE9gd_D9c5c/</link>
			<feedburner:origLink>http://blog.startika.com/2009/07/11/freckle-api/</feedburner:origLink></item>
	<item>
		<title>Weird RSpec practice.</title>
		<description>I recently found myself doing a wierd thing. While writing specs i add this spec to the end of the file:
it "should fail" do
  raise "foo"
end
The reason to do it? Simple: every time i have all the specs passing in the current file, autospec begins running all the specs ...&lt;img src="http://feeds.feedburner.com/~r/LabriasRubyBlog/~4/UIHPZZ-_o94" height="1" width="1"/&gt;</description>
		<link>http://feedproxy.google.com/~r/LabriasRubyBlog/~3/UIHPZZ-_o94/</link>
			<feedburner:origLink>http://blog.startika.com/2009/06/25/weird-rspec-practice/</feedburner:origLink></item>
	<item>
		<title>A new version of my First App. *updated*</title>
		<description>After quite some time with the docs and google (and help on IRC from some a nice guy named Sidnicious) I finally made my app behave as it should, and now it shortens the URLs you drop on it (as was requested by one of my very few users).
UPD: It ...&lt;img src="http://feeds.feedburner.com/~r/LabriasRubyBlog/~4/5Sd5BHhvkLU" height="1" width="1"/&gt;</description>
		<link>http://feedproxy.google.com/~r/LabriasRubyBlog/~3/5Sd5BHhvkLU/</link>
			<feedburner:origLink>http://blog.startika.com/2009/04/28/a-new-version-of-my-first-app/</feedburner:origLink></item>
	<item>
		<title>Heroku pricing.</title>
		<description>Heroku announced their pricing today. As with all rails-centric hosting solutions, the price is sky high. You can get a LOT more if you just go and get Amazon EC2 and set everything up yourself. Yes, they do provide you with automatic and painless scaling, but for the price difference I ...&lt;img src="http://feeds.feedburner.com/~r/LabriasRubyBlog/~4/7oCZf9Pmw3U" height="1" width="1"/&gt;</description>
		<link>http://feedproxy.google.com/~r/LabriasRubyBlog/~3/7oCZf9Pmw3U/</link>
			<feedburner:origLink>http://blog.startika.com/2009/04/24/heroku-pricing/</feedburner:origLink></item>
	<item>
		<title>My first Cocoa app.</title>
		<description>I love Objective-C.
I understood that while writing my first app, a dead simple bit.ly client. The app is a bleeding beta yet, but it works.
The thing is simple, you copy a link, run the app (from the dock, its faster to do it that way), and you get a short ...&lt;img src="http://feeds.feedburner.com/~r/LabriasRubyBlog/~4/MVKHbnx2iOE" height="1" width="1"/&gt;</description>
		<link>http://feedproxy.google.com/~r/LabriasRubyBlog/~3/MVKHbnx2iOE/</link>
			<feedburner:origLink>http://blog.startika.com/2009/04/20/my-first-cocoa-app/</feedburner:origLink></item>
</channel>
</rss>
