Quality is your “Golden” trump card

I’m a big believer in “Quality”, and its what keeps me alive in this business. Its also what attracts others to my work and that is what keeps me satisfied => to grow and grow “the right way” with the web.

Having said that its true that many people do compromise on the quality that they deliver for their clients (especially in Pakistan) and thats a real shame, to say the least….

Continue reading

37 Signals Book: Getting Real

Getting Real:  Book by 37 Signals

My hunt for knowledge usually leads me to interesting places (in Rails as well as generally). Today I found a priceless little book by 37 Signals titled “Getting Real”. The book is available for purchase here

I’ve skimmed through the free online book and it looks extremely insightful for new designers, developers etc etc coming to the Rails framework.

You might just want to check it out…

Help support Rails: Rails Activists

This is a follow up post from the one I read over at Rails Envy. Indeed its true that Rails need Active Members for their growing community, but the fact is that they don’t and this is one of the reasons Greg Pollack posted on his blog.

Read what Greg had to say:

Here in the Rails community I feel we’ve been lucky enough to have several great coders who are also great leaders. I’m not just talking about the people on the Rails core, I’m talking about people who create educational media such as rails blogs, tutorials, books, classes, screencasts, podcasts. I’m also talking about anyone who has taken the time to release a Rails Plugin or Gem, support new Rails developers (like on mailing lists, forums, or IRC), or run events promoting Rails or Ruby.

Doing this sort of community development (as you may already know), can often be a thankless job. It may feel like the people at the top (or in our case, the core developers) get all the credit. Just like I’ve heard people say “Why bother coding a Rails patch, it won’t get accepted” in regards to code, I’ve also heard “Why bother producing this Rails content, if it won’t be appreciated or recognized” in regards to community development. Thus, I’ve personally done my best to recognize and publicize these people, either by promoting them in the Rails Envy Podcast or through the Ruby Hero Awards, but sometimes I wish I could do more.

You know that this man is sincere about Rails and knows exactly where it is headed in the future. Ok, so you are not a great coder (don’t worry you will be if you take the time to). You can help out however by contributing to anyone of these destinations or by signing up:

Rails User Voice
Rails Envy => Start by commenting on their blog.
Rails Google Activist Group

Two other points that i liked (from the Rails Envy blog)

Empower People to do good work:

If you want to help with the documentation, you have an idea for a new resource, or you want to completely redo the wiki, let us know. Come to us with your ideas on how you can support the community on the internet or even in your local neighborhood. Lets figure out how we can help you spread the word.

Listen to the community

I care a great deal about growing Rails in 2009, and pushing it deeper into the enterprise. Each of the Activists has their own initiatives and projects to help do this, but we’re going to need community involvement to attack some of the bigger issues. Two examples of this might include fixing the Wiki, and the creation of some sort of Rails Book.

Valid points by Greg no doubt, so let the Rails Core team do what they do best => and that is program. I for one will help out wherever i can, even if it means spending extra hours on the computer aside all my other work..

Class Declarations in Rails Migrations

This is an unforgettable mistake i made today while running some migrations in Rails.

Here is the first migration file. It was generated by using this simple command:

ruby script/generate model Articles

Simple enough right? The output of the generation was:

When i went ahead and tried the rake command to migrate to my database: rake db:migrate I kept getting an error “Uninitialized constant Create Articles” Rake Aborted!!

Having forgot that everything in Rails is Object Orientated (extends from one base class or another) i overlooked two things.

  1. I did not declare the class and what base it extended
  2. I did not add the schema file name into my migration file

Usually Rails generates the schema and adds the base class (Active Record) but this time it didn’t. Anyhow the fix was easy enough…

So this is a classic mistake of us all having our moments..Thanks again to the users over at Stack Overflow for helping out. Their are some excellent trouble shooters out there.

New Relic: Monitor your Rails Apps without fuss!

New Relic:  Monitor Your Rails Apps

RPM Lite is a FREE, supported Rails production monitoring product that helps you keep your app humming. You get deep, real-time visibility into your app, so you always know what’s up. Use it on as many applications and hosts as you like. For as long as you like.

Troubleshoot in development. Troubleshoot in production. Build high speed into your app from the very beginning.

Sign up for New Relic (its free!!)

I spent two minutes checking it out with the *small flex/rails app that i made the other day. What i liked straight off the bat was two things:

  1. Installing the plugin: Easy as pie! I’m not exactly sure if you can install it without signing up, nevertheless it was a cinch!
  2. Point and Go!: All you got to do is point your browser to:
    http://localhost:3000/newrelic and you are done!!

New Relic:  Easy to install and get your performance stats!

So its pretty much a straight outta the box type of deal here. Will definitely be using this little baby from now on!