Working With Rails

schema

Watch > Robotagger: GML +...

Watch > Robotagger: GML + ABB4400 http://mag.ma/greg/343068

Rolling your own

goat

"Don’t confuse legibility with communication. Just because something’s legible,..."

adamlogic: @AdamWinter Make that Danny's, although I imagine you're eating by now.

Hidden Treasures when staying in Lake District Cottages

Maple Tree Funding – Your Source for Home Loan Solutions & Best Options For Your Mortgage

Home Buying Both Supports and Takes Advantage of the Current Economy

Twitter Updates for 2010-01-13

adamlogic: @AdamWinter We ended up going to meijer first. Now headed to Manny's up th road if you care to join.

Watwet from Apie [13/01/2010 01:47]

Official Google Blog: A new approach to China

(posted by RIMBoy)

2010 – Novas promessas

"That’s why I use grids. For me it’s a tool for creating order. And creating order is..."

Watwet from Apie [13/01/2010 01:17]

laughingsquid: I’m With Coco

laughingsquid:

I’m With Coco

hello, lover…

links for 2010-01-12

Has your website gone mobile?

adamlogic: @alycit of course! ;-)

Easy Testing MongoMapper models

There's a bunch of libraries to write tests easily for your app. factory_girl and Machinist for the fixtures. Remarkable for the macros.

There's no core support for MongoMapper in any of these solutions but Machinist and Remarkable are agnostic so it's easy to add a MongoMapper support. That's what I did a few months ago with machinist_mongo and remarkable_mongo.

I'm refactoring them to add Mongoid support in a near future and I think it's time to have a bit of docs on these 2 gems. Let's see how to use them in a Rails project with RSpec.

Machinist for MongoMapper

First we load the gem:

Then it's like any other Machinist adapter. We create the blueprint:

We require the blueprints.rb file into spec_helper.rb:

We write the specs:

And finally the related model:

Like Machinist for ActiveRecord you have the 3 following methods: Model.make, Model.make_unsaved, Model.plan. And there's a preliminary support for embedded documents.

Remarkable for MongoMapper

The first step is the same that Machinist, requiring the gems:

Let's add the specs. Say we want to check the existence of title and body keys and the title presence validation:

Finally we modify the model to pass the specs:

Remarkable for MongoMapper is not feature complete (as of v0.1.2). Here's the list of macros but they don't support all the options of the related MongoMapper methods.

• belong_to
• have_many
• have_key/have_keys
• validate_presence_of
• validate_confirmation_of
• validate_length_of (bugged)
• allow_values_for

If you want to add features, fork the repo.

Conclusion

If you've already used Machinist and/or Remarkable you won't have problems. For the other ones it is an easy solution to write your tests quickly.

adamlogic: Dinner, anyone? #codemash

dambalah’s api-throttling

Rack Middleware to impose a rate limit on a web service. Blog post.

adamlogic: Thanks @surfacedamage for stocking our fridge at #codemash (of course we cracked them open first thing) http://yfrog.com/3lkezj

Watwet from Apie [13/01/2010 00:47]

Watwet from George [13/01/2010 00:47]

Watwet from George [13/01/2010 00:46]

Watwet from George [13/01/2010 00:43]

Giant Spider Species Discovered in Middle Eastern Sand Dunes | Wired Science | Wired.com

(posted by RIMBoy)

Scary Ruby

We all know that Ruby’s a flexible beast, but just how much you can bend it is almost scary. How about inheriting from a class randomly chosen at runtime? Sure, no problem:

I dare you to find a use case for this

And in case random isn’t good enough for you, why not have the user choose the superclass for you?

Small Business Accounting Software

my improvements on latest i18n gem

In recent weeks I spent a lot of time on i18n stuff in project I currently working on, so I was really happy, after I read José Valim’s article about new i18n gem, which has been very improved and introduces new features (Thanks José for great article and benchmarks).

Unfortunately, after few days of using it I noticed few issues (which I reported on http://github.com/svenfuchs/i18n/issues. They were related to I18n::Backend::Fallbacks, which handled only translation method, and does not localize, pluralize and :default option, also I18n:Backend::Fast threw an exception when there were no translations for locale or one of locale fallbacks. Because I need all these 3 backends, they blocked using new i18n :(

$ braid add -p git@github.com:knapo/i18n.git

def reload_i18n!
  $:.grep(/i18n/).each { |path| $:.delete(path) }
  I18n::Backend.send :remove_const, "Simple" 
  $: << Rails.root.join('vendor/plugins/i18n/lib').to_s
end

reload_i18n!

module I18n
  module Backend
    class Knapo < Simple
      include I18n::Backend::Pluralization
      include I18n::Backend::Fallbacks
      include I18n::Backend::Fast
      include I18n::Backend::InterpolationCompiler
    end
  end
I18n.backend = I18n::Backend::Knapo.new

actionpack-2.3.5/lib/action_view/locale/en.yml
activesupport-2.3.5/lib/active_support/locale/en.yml
activerecord-2.3.5/lib/active_record/locale/en.yml

But actually it might be a feature for some devs (e.g. me:) ), I copied them into my locales dir to active_support, active_record and action_view subdirs, and have all translations file in one place, and it’s better to have default (en) Rails ones there to easily compare other locale files with them, and/or edit them.

• I18n::LoadPath which makes I18n.load_path more handy:

      I18n.load_path = I18n::LoadPath.new(I18n.load_path)
      I18n.load_path << Rails.root.join('locales/pl.yml') # loads single translation file
      I18n.load_path << Rails.root.join('locales') # loads all translation data files in specific directory
      I18n.load_path << Rails.root.join('locales/*.{yml,rb}') # loads all translation data files  by given pattern
    

• I18n.wih_locale which executes block in given locale set

       I18n.with_locale("pl-PL") do
          # This code are being executed with pl-PL locale
       end
    

• Making MissingTranslation message thrown by I18n.localize method complete, as previously when translation was missing it returned partial message e.g. for I18n.l Time.now, :format => :missing I was getting: translation missing: en, long_ordinal, what was misleading and now I’ve got: translation missing: en, time, formats, long_ordinal

The only thing I really don’t like in new i18n is forcing I18n.locale to Symbol – why? it should absolutely be a String

Anyway, thanks to Rails i18n team for great improvements on i18n, and looking forward for fixed issues in next gem version (and Rails3, of course).

2010 - The Year Ahead

2009 was a very interesting year, a year of some realization and a year which helped lay the foundation for the year ahead and hopefully the future.

I decided to document here a bit of what I have on my mind for 2010, not New Years Resolutions, I hate those and never do them. I have gained a fair following of loyal readers over the years and think of you as family, so I thought I would share with my blog family.

Freelancing

As I said in my previous post, I have been freelancing for many years and in 2009 I realized the ability and desire to continue with freelancing as a full-time endeavor was difficult. I will not be pursuing freelancing full-time in 2010 and as the year progresses I see the time spent freelancing to be less and less.

I will continue to work with selected clients as I have a vested interest in their success. In time I imagine their need for my services will be less and less.

I will be open for consulting opportunities with the possibility of part-ownership in a product and/ or for projects that need help figuring out difficult problems in areas I have expertise in but not limited to .NET to Rails migrations as well as scalable ecommerce systems.

Products

Even before I was in college I have always wanted to have an idea for a product, develop it, successfully market it and support it. I have been involved in a product company in the past but not my own individual ideas. I am sure this sounds self-serving, and it is, but there comes a time when we need to decide what is important and do it.

So, my goal is to primarily be a product company by the end of 2010. The company is Still River Software Company, LLC, which has been the umbrella I have been providing freelance services for the past 3.5 years.

Things are progressing nicely in a couple of exciting areas, so new product announcements will be coming soon. Very soon, but not just yet.

Blogging

I have not blogged a lot lately, been too busy with the business side of life. I will be blogging here, mainly about technology trends and my usual odd opinions about some aspects of technology and may begin to add some business writing as well which covers certain aspects of running a software company.

I will also be opening up a new blog for Still River Software which will discuss very company-specific information, including product releases and such. I will announce it here when it's ready, please check it out.

Conferences

I have not attended as many conferences as I hoped to in 2009, the ones I did attend were developer-related, mainly Ruby. In 2010 I intend to attend more conferences but probably more in line with running a business or software company more specifically. I hope to see you there.

So, I hope the ride is nice and I hope I can report back great success at the end of the year, I certainly expect it.

Watwet from Apie [13/01/2010 00:17]

Watwet from Apie [13/01/2010 00:17]

Watwet from Apie [13/01/2010 00:17]

What are the Advantages of Scrum for the Client?

Scrum provides many benefits for developers, but what are the advantages of Scrum for the client and other stakeholders? This is a question I faced yesterday in a client meeting.

To answer that I need to define what is Scrum. In layman terms, it is a project management technique that is used with agile development projects.

Benefits for the client:

First of all, Scrum facilitates changing customer requirements. It provides a flexible framework where addition of new features or re-prioritization can take place without negatively affecting the project flow and team's morale.

Secondly, it encourages regular feedback by having short development cycles (sprints), where at the end of each sprint a review takes place. The review provides opportunity for the entire team to reflect on the last sprint and improve.

Thirdly, by defining roles for team members it promotes collaboration as well as clear and open lines of communication between developers, the client and other stakeholders.

Finally, Scrum provides a framework for work estimation, where features are estimated using points. Each point represents a relative amount of effort required. The technique is flexible enough to allow for changes in requirements as well as changes in development teams velocity.

However, Scrum is not always suitable and does not always work:

It does not work with traditional software development methodologies such as Waterfall.

It cannot be fully adopted if a team is too small or too big - ideal team would be 4 to 6 developers.

It cannot work effectively if it does not have full management/client support.

It requires a Scrum Master who understands the Scrum practices and is able to apply them.

Permalink | Leave a comment  »

RE: Для ознакомления с другими проектами

Для ознакомления с другими проектами

SSI Racing Announces 10 Year, 100 Percent Guaranteed Automotive Battery and Limited Edition Full Custom Electric Vehicle

Tips on “Green” Travel

How to Hire a Limo for Your Prom?

Clint Dempsey’s Early Submission For Prem Goal Of 2010 - - The Offside - Soccer News and Opinion from leagues around the world

(posted by arafatm)

Hitler’s letterhead….

(posted by arafatm) zoom

(posted by arafatm) zoom