Hi, I'm looking for qualified Ruby on Rails developers to work on a
client web portal project in Midtown Manhattan for a large financial
research company.
Ruby / Ruby on Rails developer with strong object oriented programming
background. Good understanding of model driven architecture, MVC, RDBS
and data modeling.
- BS. in Computer Science (or closely related field)
- 1+ years of Ruby on Rails or 2+ years predominantly using the Ruby
language
- Demonstrated experience/knowledge building high-volume and customer
facing database-driven web applications.
- Experience building n-tier Internet applications in Ruby on Rails
- Strong object-oriented design and development skills
- Good understanding of test-driven development methodology
- Thorough knowledge of relational databases, schema design and
implementation, and SQL query design.
- Hands on experience with Javascript, AJAX, HTTP, XHTML and Web
Services using both SOAP and REST.
- Good ability to translate requirements and functional specifications
into working applications with minimum guidance.
- Good communication skills and ability to interface with business
users
Majority of work must be done on site at client.
* Compensation: Negotiable: Hourly, daily or fixed price
* This is a contract job.
* Principals only. Recruiters, please don't contact this job
poster.
* Please, no phone calls about this job!
Most of this community is not in Manhattan so If you can set things up
so we can telecommute you might get a couple resumes.
--
Posted via http://www.ruby-forum.com/.
you saw nothing
> * Why omit the company name?
> Because there are contract whores who will be more interested in the
> Gold Plate than the actual work to be done.
More likely that the job posting is from a head hunter who is trying
to keep prospective respondents from bypassing them and their
commission.
And often when two job postings look suspiciously familiar it's
because they are from two different head hunters competing to fill the
same job for the same client.
--
Rick DeNatale
My blog on Ruby
http://talklikeaduck.denhaven2.com/
@John, I couldn't agree more. It's almost fruitless to respond to
each of the points, but here are some of the main ones:
* Why omit the company name?
Because there are contract whores who will be more interested in the
Gold Plate than the actual work to be done. The absolute insistence
here on getting a company name certainly reflects that. By avoiding
the name the poster actually will get people who are interested in
_doing the work_. The more you advance in your career the more that
you'll recognize that the type of work that you do is generally more
important than the name on the check you receive (well, the one
besides yours anyway).
* RoR = OOP, MVC?
Yes, Rails is an Object oriented, MVC framework, but that does not
mean that every RoR hack is very good at OOP or MVC. For example, the
Google group post that I followed to your blog and eventually here did
a great job... of mixing business logic into the controller. THAT IS
NOT MVC. The previous one explained how to set a bit ("default") on
one object in a collection. Simple enough, but what the recommended
solution did not recognize was that the action was really an action
that dealt with the collection and that setting that 'default'
attribute on one object in the collection was just a mechanical means
to an end. That was poor OOP. Physician, heal thyself.
* 2+ yrs of Ruby or 1+ yrs Ruby on Rails
This is one of the worst offenses in this "insightful" dissection.
The implication is that there are developers in the world whose
primary work has been in Ruby but with absolutely no use of Rails.
For example, there are several GUI frameworks that make cross-platform
desktop development possible in Ruby. A friend of mine has written
some beautiful code that does very efficient bitmap processing as a
command line utility. Again, no Rails but plenty of beautiful Ruby.
What the Rails community in general should recognize, as this
financial firm in Manhattan has, is that a solid knowledge of Ruby is
*more* important that Rails experience. That is, a great Ruby
programmer with no Rails experience will be much more productive than
a Rails hack with no real Ruby knowledge. You might consider these
broader implications before pontificating.
* Javascript is AJAX!
No, it's not. As elsewhere you seem to fail to recognize that it's an
instance in a collection.
AJAX is Javascript. The relationship is
the other way around.
AJAX is a very specific use of Javascript and
it you simply rely on the Rails helpers (I suspect that you do) then
you have a great deal to learn.