> I've been trying to find either a full time or series of part time
> gigs, preferably doing ruby with or without rails.
Hard to imagine any Rails developers needing work. We're always
looking for contractors with the right skill set for the right price.
Seems like there is *way* more demand for Rails work than there is
supply.
Or maybe my experience is not that of the rest of the world?
Colin
Colin A. Bartlett
Kinetic Web Solutions
http://blog.kineticweb.com
We've been vetting lots of applicants from headhunters in NYC and SF
in the past few months for some of our clients who are transitioning
to their own fulltime team.
Here are some useful hints after looking at tens of applicants. If
you want to work at the top tier, you need to fulfil most of these, or
have a pretty damn good answer as to why you don't. I've included
approximately how many people actually do this.
1. Link to your github profile. Don't have one? Make one, fork some
OSS projects, do some work on them. Write a plugin. Etc. (5% of
people do this)
2. Include a brief cover letter where you talk about your experience. (80%)
3. Include a full rails app that runs out of the box which shows your
level of proficiency in rails. If you have some crazy polymorphic
joins or advanced features, be prepared to explain why you did it that
way. (10%)
4. Include some non-rails ruby code. (10%)
5. Include a single test for your ruby code (2%)
6. Include a full test suite for your ruby or rails code (1%)
That's right, about one out of all the applicants actually included a
full test suite.
7. Talk about your testing philosophy and how you apply it to your
development workflow (1%)
So as you can see, the bar is pretty low, if you're a solid developer
who has written a few plugins or released/patched some open source
projects, who writes tests and can talk about a best practice
development process. If you don't do all of these things, we
definitely wouldn't hire you or recommend you to our clients.
If you write unit, integration, acceptance, ui tests, have released
your own frameworks, test harnesses, or other interesting ruby code,
then you're at the top of the heap.
Unfortunately, there are a LOT of developers out there who don't meet
these criteria, so if you're looking for work, start there.
Courtenay
To be fair, I haven't shaken all the trees in my forest yet, so....
Wes Gamble
If you're in NYC, we have a client looking for developers. They're
working on some cool stuff, changing the world for the better.
Contact me :)
Courtenay
Wow, I'm surprised to hear how low the bar is. I thought just about
all Rails developers had Github accounts, open source contributions,
well-tested code, etc.
-TJ
Oh god, it's a wasteland out there beyond the city walls. Zombies and
cargo cults.
I'm with TJ. I know we tend to surround ourselves with people probably
ahead of the game (you know, people who attend user groups, have a
desire to improve themselves, share similar values), but those
percentages from Court3nay are astonishing.
+1 for Tom sending everyone on this list to the sales team. I'm in the
market for more freelance gigs as well, and figure if Rick can't get
more work in the same market I'm in...
--
Christopher Redinger
http://www.agiledisciple.com
That's exactly what it is. I've always felt that I wasn't really an
expert in anything (rails, php, sysadmin, etc.). Part of that was
working with the same group of folks for about 8 years, we all just
did our thing and all was well. When we finally split up there were
jobs I wouldn't apply for because they wanted "linux" and I knew
"freebsd". My wife sat me down and told me to stop being silly! She
said the reason I felt like that was because the people "i knew" and
"looked to" where the people who *wrote* the software in the first
place -- not the entire pool of developers. She's right of course
(and as usual :) but it took me awhile to adjust to that.
> +1 for Tom sending everyone on this list to the sales team. I'm in the
> market for more freelance gigs as well, and figure if Rick can't get
> more work in the same market I'm in...
Just had a new business idea! http://rails-cage-fights.com. First
bout... Rick vs Christopher! It would be like Mad Max, but more
geeky... ha ha. Cha-ching! :-)
Oh man, you'd need some seeding (and not the funding kind). Chris and
Rick are both high seeds. You can't match them up early on!. :)
BTW, I know both Chris and Rick and recommend each highly, FWIW.
-TJ
+1 mirrorplacement as well. Brian's clearly head and shoulders above
other recruiters.
Gravity People is also extremely good.
Will.
> I was wondering if anyone had any recommendations on someone who would be
> good to work with.
You may consider joining the Ruby on Rails group at LinkedIn, if you
haven't done so already. The group has just under 3,000 members at
the moment, including a number of head hunters. I cannot vouch for the
quality of the head hunters, though.
Find it here - http://tinyurl.com/ror-linkedin
Then start a new discussion to market yourself. If that is written
well, with a good subject, you may some good responses.
Good luck!
--
rgrds,
Johan
1) Which testing framework(s) do you currently use? (test:unit, rspec, shoulda, etc.)
2) Which testing framework(s) do you look for ideal candidates to have experience with (if it matters at all to you)?
Thanks!
-John
rspec exclusively
> 2) Which testing framework(s) do you look for ideal candidates to
> have experience with (if it matters at all to you)?
rspec, but any testing experience is a plus!
Let me preface this by saying that I've no intention to start a framework war here (Obie's already taken the "controversial post" award for this month!), but I'm curious for my own reasons. For those of you who are looking for employees/freelancers, could you weigh in on these two questions:
1) Which testing framework(s) do you currently use? (test:unit, rspec, shoulda, etc.)
2) Which testing framework(s) do you look for ideal candidates to have experience with (if it matters at all to you)?
Thanks!
-John
> Let me preface this by saying that I've no intention to start a framework war here (Obie's already taken the "controversial post" award for this month!), but I'm curious for my own reasons. For those of you who are looking for employees/freelancers, could you weigh in on these two questions:
>
> 1) Which testing framework(s) do you currently use? (test:unit, rspec, shoulda, etc.)
assert{ 2.0 }
via Test::Unit (and a little test-spec) at work.
RSpec when I'm researching Merb, but that's just because the framework (and
community) tends to bend you over and shove it where the sun don't shine...
> 2) Which testing framework(s) do you look for ideal candidates to have experience with (if it matters at all to you)?
A candidate who tests?
BWA-HA-HA-HA-HAW that's a good one!!
--
Phlip
1) Which testing framework(s) do you currently use? (test:unit, rspec, shoulda, etc.)
2) Which testing framework(s) do you look for ideal candidates to have experience with (if it matters at all to you)?
I use a mix of RSpec and Test::Unit. And any test experience is good,
as long as they understand the workflow of TDD. Test frameworks are
like languages, the syntax matters far less than the mindset of how
you address problems. If I were doing a regular kind of interview,
I'd ask them about mocking and fixtures more than what test framework
they used.
--
Josh Susser
http://blog.hasmanythrough.com
Golden Gate Ruby Conf :: April 17-18 :: http://gogaruco.com
1) rspec + fixture_replacement + unit_record
2) Any
Will.
shoulda/test::unit + mocha + machinist. I'm learning cucumber but
didn't add it to my day-to-day workflow yet.
>> 2) Which testing framework(s) do you look for ideal candidates to have experience with (if it matters at all to you)?
Any.
--
Raul Murciano - Freelance Web Developer
http://raul.murciano.net
Shoulda
> 2) Which testing framework(s) do you look for ideal candidates to
> have experience with (if it matters at all to you)?
Same as most of the others, it doesn't actually matter as long as they
have TDD experience.
-Chad
---
Chad Pytel, Founder and CEO
thoughtbot, inc.
organic brains. digital solutions.
-------------------------------------------
tel: 617.482.1300 x113
fax: 866.217.5992
http://www.thoughtbot.com
Let me preface this by saying that I've no intention to start a framework war here (Obie's already taken the "controversial post" award for this month!), but I'm curious for my own reasons. For those of you who are looking for employees/freelancers, could you weigh in on these two questions:
1) Which testing framework(s) do you currently use? (test:unit, rspec, shoulda, etc.)
2) Which testing framework(s) do you look for ideal candidates to have experience with (if it matters at all to you)?
| Total: 667 votes Haven't voted yet? Go here to vote! | |
|
| test/unit [ 22% (144 votes) ] |
| rspec [ 54% (359 votes) ] |
|
| shoulda [ 16% (104 votes) ] |
|
| context [ 2% (13 votes) ] |
|
| other [ 7% (47 votes) ] |
RSpec with cucumber for my stuff. Vanilla Test::Unit for legacy
projects (I'm not going to rewrite 900+ test cases).
> 2) Which testing framework(s) do you look for
> ideal candidates to have experience with (if it matters at all to
> you)?
*. I'm happy to see people just trying to test. I get enough patches
without tests and with glaring bugs already. Even a:
def test_if_password_is_secure
# TODO: not sure how to test this
end
would be great, then you know their at least thinking about testing
their code.
--
Eric Davis
Little Stream Software
http://www.LittleStreamSoftware.com