addressalign-toparrow-leftarrow-rightbackbellblockcalendarcameraccwchatcheckchevron-downchevron-leftchevron-rightchevron-small-downchevron-small-leftchevron-small-rightchevron-small-upchevron-upcircle-with-checkcircle-with-crosscircle-with-pluscrossdots-three-verticaleditemptyheartexporteye-with-lineeyefacebookfolderfullheartglobegmailgoogleimageimagesinstagramlinklocation-pinmagnifying-glassmailminusmoremuplabelShape 3 + Rectangle 1outlookpersonplusprice-ribbonImported LayersImported LayersImported Layersshieldstartickettrashtriangle-downtriangle-uptwitteruseryahoo

Re: [ruby-112] From a business perspective is it a good idea to build in Rails?

From: Sam R.
Sent on: Tuesday, April 15, 2014 4:34 PM

I have to say I'm not really clear on what is mean by junior/intermed/senior here... generally it refers to pay scale, which roughly corresponds to some mix of years working+specific abilities.

I've hired hot devs right out of school who were very sharp and knowledgable about a few important things, and most importantly, when they didn't know something that came up at work, they did the next day. Truly a pleasure to work with, some of the most productive developers I've worked with are like that, and I've learned a lot from them. Some of them have been generous to say they've learned from me, too.

I've also seen seemingly experienced in years developers who didn't even know how to configure their text editor to conform to our code style. Ouch.

I've also worked with devs with years of experience who have written their own lisp interpreters, then bootstrapped them into successful companies... that's a learning experience.

And everything in between.

Also, as someone who I guess would be called "senior", I've been hired into companies to work on frameworks where I didn't know even the language they were written in, much less have experience with the framework, but I could get hired in because of broad background in technology, and demonstration that I get stuff done.

Specifically in terms of Rails, I suspect companies want to hire someone who either can demonstrate Rails experience, or solid experience around a few similar technologies, or just that they are very convincing polyglot fast-starters.

So experience isn't a sliding-scale, its more of a weird pyramid. The less specific your experience to the position is, the broader and deeper that experience should be.

If you know nothing but Rails, but know it well, that will work, you can learn the other stuff.

If you know no rails at all, but have lots and lots of experience across a **range** of different technologies, then you should be able to get productive with Rails pretty quickly.

And if you are a shallow puddle, where you just know a tiny bit about not very much... that isn't good.

If on top of that you don't have any open source commits to your record, you don't have a project to show on github, you don't read any blogs, you can't name any information sources you are using to improve your knowledge, and something you've learned in the last few weeks, and you've not read a book in the last year, ...

In short, you appear to know nothing but what they told you in your school classes... this is really, really not good, no matter what your grades were. Don't be that person.


Our Sponsors

  • Brewhouse

    Vancouver's leading product development studio

  • CodeCore

    Build Rails Apps in 9 Weeks! Full-Time and Part-Time Development Program

People in this
Meetup are also in:

Sign up

Meetup members, Log in

By clicking "Sign up" or "Sign up using Facebook", you confirm that you accept our Terms of Service & Privacy Policy