• Myth #1: Rails is hard to deploy
• Myth #2: Rails is expected to crash 400 times/day
• Myth #3: Rails forces you to use Prototype
• Myth #4: Rails is a monolith
• Myth #5: Rails is hard because of Ruby

when you don’t create things, you become defined by your tastes rather than ability. your tastes only narrow & exclude people. so create.

But I always had question, how OpenID solves the problem of multiple login ids.
Suppose today you like http://claimid.com as OpenID provider,
tomorrow you might like different OpenID provider. So if you create a new OpenID,
you will use this new OpenID to logging in to OpenID enabled sites.
Then what about previously using OpenID, what about all previous accounts created with it.

For all your previous accounts, if you want to keep the same account on site, you
need to login with your old OpenID, . If you try to use new one, it will be treated as
new OpenID and new account to the site. So finally using OpenIDs results into using
multiple OpenIDs. That’s why, I was really not impressed with OpenID concept.

But today, I came to know about this great concept, OpenID delegation.
Its very simple and clean concept. What is it?

Delegation allows you to use your own website as your identifier while
still using a third-party OpenID provider. This requires only the
ability to add a small snippet of HTML code to the page you wish to
use as your identifier.

So you can use your own website address as OpenID, in my case it is anilwadghule.com.
You could setup delegation with any of OpenIDs. You could keep changing your OpenID
from OpenID providers and just use your site address as delegated OpenID.

You need to add following code to your sites index.html or any index page, which gets
rendered when you hit yoursite.com

<link rel="openid.server" href="https://www.myopenid.com/server">
<link rel="openid.delegate" href="http://anildigital.myopenid.com">

Now you can use your website address as your OpenID. Thats it.
In my case it is anilwadghule.com

Now you don’t want myOpenID as OpenID provider and you think claimid.com is better OpenID
provider just replace above snippet with code

<link rel="openid.server" href="http://openid.claimid.com/server" />
<link rel="openid.delegate" href="http://openid.claimid.com/anildigital" />

And now you can still use your delegated OpenID to login to different OpenID enabled
websites.

Awesome right?. So go start using your website address as OpenID!

You should always have a side project, too. Side projects give you an
outlet, provide a useful distraction, let you explore new ideas, learn
new concepts, and generally give you the freedom to be unaccountable.
You don’t have to worry about your boss, or your coworkers, or the
damn commentators on Reddit. Just have some fun. Treat yourself.

If you already have a job you love, this doesn’t exclude you. You
probably use, day to day, many side projects from others. You can
also use your own side projects at your job. From Emacs configs to
simple web services, there are a ton of things you can do to stretch
your brain.

So, start a side project. Who knows where it will take you.

Do you have one now? If not, why not? Not enough time? No ideas? I
think I can help with both of those.

First off, the time issue. I don’t know how many of you read RSS, but
I challenge you (that’s a keynote term) to give it up for a month.
Just turn it off. Stop using Google Reader or NetNewsWire or whatever
the kids are using these days. It’s not worth your time.

What should you do instead? If you use Twitter, try following the
authors of your favorite blogs. Read their tweets on the bus. Or in
the bathroom. Check Ruby Inside once a week and skim over the posts.
Visit an aggregator like planetrubyonrails.com once a month. But
mainly, let other people do the filtering for you. Use your time for
other things.

You will not miss out on anything big. Stuff like the Google App
Engine, or Rubinius running Rails, or the killer speaker line up at
this year’s Ruby Hoedown will find its way to you. How can it not?
I’m willing to bet a lot of the stuff in your RSS reader is stuff you
already knew, or heard about somewhere else.

Personally, I used to check RSS multiple times per day. Now I don’t
use any reader, and haven’t since January 2008.
Another big time sink among programmers, I’ve found, are books on
process and theory. Books like Smalltalk Best Practice Patterns,
Practices of an Agile Developer, and even, I dare say, the Pragmatic
Programmer, are not worth your time. Instead, listen to Rein’s talk.

Talk to your friends or coworkers. Let other people filter the
information for you, then decide what you like.
The best way to learn about patterns, idioms, and best practices is to
read open source code. See how other people are doing it. It’s a
great way to stay current, and it’s free.

Next implement the Jerry Seinfield GTD method. Every time you work on
your side project, mark a big X through that day on calendar.
Eventually you’ll have a nice line of Xs. Missing an X will be
torture - it’ll mess up your beautiful streak. The goal is to maintain
the streak, even if you don’t think you have any ideas for the day.
The best way to overcome writer’s block is to write, after all.

Okay, so the time excuse is gone. Now you have time to work on a side
project and the motivation to do it consistently - the beautiful line
of Xs. You can devote at least one Sunday a month to it, at least.
But what’s the idea?

This is actually the easy part, because you don’t need a good idea.
Just start doing something interesting. Play with a new framework in
Ruby - I hear Sinatra is pretty hot these days. Learn how to do GUI
stuff, with Shoes.

Learn JavaScript. Like, for real. If you don’t know what the var,
with, or delete keywords are, get a book and start working on some
flashy effects. Or download Rhino or Johnson and write some server
side JS. It’s a really beautiful and misunderstood language.
Take some time to master your editor. Pick up the TextMate book and
dive in. Write a bundle. If you’re already got massive Vim-fu, try
out Emacs. Learn why people love it, then use that information in
your holy wars against them.

Write a web service. Something like Cheat, Subtlety, Disqus, or
TwitPic - tools someone can use to help make running a blog, site, or
coding simpler. Simple sites that do one thing very well, and surface
their information with digestible APIs.

If you’ve been meaning to learn a new language, start learning it.
But don’t just read a book. Start writing a program.

Learn Objective-C and Cocoa. Write a little Mac app to do something
useful, then give it away for free. Post the code on GitHub. Put up

a Pledgie badge and accept donations. Profit.

Write Rake in a Lisp. It’s a good way to learn about metaprogramming
and how command line scripts work in your new language. Write an RSS
parser and explore native data types in Erlang. Write a simple blog
and learn about the web frameworks in Haskell. Write Scrabble in Io,
picking up some OpenGL along the way. It doesn’t matter if people
have done it before.

In fact, stop worrying so much about other people. Every time I’ve
worked on a project I thought other people would really love, it was a
massive flop. Every time I’ve worked on a project I loved, it worked.

If you’re sitting in this room, your taste is not as far off from
those around you as you’d think. Build something you love and others
will love it, too. (Not everyone, of course.)

Alternatively, do something hard, the hardest thing you can think of,
in your language of choice. Stretch the boundries. Make Ruby cry out
in pain. Install ImageMagick. Rewrite all of the standard library.

Write an Objective-C bridge. You know, something just devilish. Flex
your brain.

Work on your small project for a few Sundays, declare it complete then
move on. Learn another language, or write something else in your new
language. Pick up a new web framework or work on flashy effect number
two. Add concurrent task execution to your Rake. The more acclimated
you get to this process, the more creative your ideas will be. It’s
the whole 10% inspiration 90% perspiration thing, and it worked for
me.

This, after all, is how GitHub was started. Tom and I had full time
gigs, but we’d get together on Saturday, have lunch, then work on
GitHub. We wanted a pretty and simple way to share Git repositories.
Something we’d use. Something that would make it easier for us to
share and work on open source.

The more side projects I had, the more I felt the pain of maintaining
open source code.

My plea to you today is to start a side project. Scratch your own
itch. Be creative. Share something with the world, or keep it to
yourself.

Side projects are less masturbatory than reading RSS, often more
useful than MobileMe, more educational than the comments on Reddit,
and usually more fun than listening to keynotes.

It’s a A List Apart’s survey 2008 for people who make websites. I came to know about this via Abdul’s blog. Questions were really interesting. Do take the survey.

Planet site aggregates feeds of different weblogs into one site. It’s having RSS feed support, so if you subscribe the RSS feed of it, you will never miss posts by your favorite Rails blogs. If you already know existing most popular Rails planet site by Pratik, you know what Planet is.

I have added only few feed channels to it those I like. Mainly to have quality content. Feel free to contact to for adding you popular Rails weblog to the planet. I would definitely try to add it.

On the technical side, I am using my Slicehost slice for hosting it. Mongrel + Nginx combo. It’s using Rails. It is open source you could check its source here. Apart from those thanks to Capistrano + Git which makes development so enjoyable without pain. I see my planet as defacto site to read great Rails posts.

If you find Planet site/source useful please donate 
 
(Blog authors who don’t want to have their posts to be displayed in Planet, feel free to contact, I would happily remove feed).

Some days ago, I forked koz-rails(Rails repo git mirror) repository, considering that I would start hacking Rails source. I had no idea that Rails would officially move to Git that time. I had read some posts of Koz that it is not that easy to start using Git to manage Rails source. But now after reading DHHs announcement post, I am happy.

The good thing is that it will use GitHub (awesome Git repository hosting site). I am in love with GitHub since I heard about it. I think, I am one of the earlier users of GitHub and that makes it and me special that Rails is using GitHub.

Even DHH himself has written good words about Git and GitHub. Chris also wrote some posts related to this announcement.

I always find that like minded people like similar things and it continues. I also noticed that whatever I like becomes Hit and popular(oh yeah). I think I have some little sense to predict about any app and its future. I think I can definitely define product features for a successful app. I think I also understand the market and what people want and expect. This is why I am more eager to develop my side projects.

Update 12 April, 08: You could visit Rails repository at http://github.com/rails/rails/tree./

For cloning do

git clone git://github.com/rails/rails.git

My fork for Rails is at http://github.com/anildigital/rails/tree

When I started my career with Ruby on Rails, Pratik too had started working Ruby on Rails in those days. Pratik also was working with Betterlabs and I was with Reevik Technologies. There were only two companies in Pune, which were using Ruby and Ruby on Rails for projects. We used to meet at various Ruby meets in Pune.

I would like to thank Pratik for gifting me domain names anilw.info and anil.rails.in with server spaces. One of the reasons I continued career in Ruby on Rails is Pratik. We have been discussing about tech topics IRCs, messengers, twitters for sometime. He always helped/guided me. He is nice guy. I congratulate him for his achievement and greatness. Great work man! He currently works with a London based startup(makers of Bebo and BirthdayAlarm.com). Do check out his nice blog, http://m.onkey.org.