gisikw

Move Fast and Break Things

Some of the behavior of the site varies based on whether or not you're on a touch device - we're keenly aware of there being different usability concerns between desktop and mobile devices. But your point is well-taken. If there are specific areas where we're preserving a particular desktop-esque or mobile-esque paradigm at the expense of UX, it's probably something we need to address.

It's largely a semantics game. Some people use one to refer to device-responsiveness versus screen-resolution-adaptiveness. Under that definition, both apply to our redesign :-)

Yep. Filled out that title box and the URL box and everything.

...oh, oh, you mean the redesign. Yeah, that too.

Is this not how we hire writers?!

"Years of Experience" along with "Degree" are objective requirements that can simplify hiring. Some companies will be hard and fast about them, others will be more flexible.

But to note, if you want to claim that you have outstanding reasons why lack of years, or a degree, or a certification, or whatever ought to be disregarded, figure out why that is, and emphasize it.

If you have an active GitHub profile, an interesting blog, a self-published book - a great many recruiters will overlook their objective benchmarks.

Focus on your strengths, shore them up, and advertise them. Time wasted complaining that some recruiters are inflexible is not only pointless; it takes time away that you could be using to do something positive.

I don't understand this. Selective dissemination of actual business data - fine, sue their asses. But projections are guesses - guesses without any guarantees. Facebook could magically rake in a billion tomorrow, or completely shut down - "projections" aside.

Why is it that there's a legal recourse because the projections person X got were different from what person Y got?

Having your lawyer read something is no excuse for not also reading it yourself.

Because alcoholism and lethargy primarily harm the self - rather than others. Sexism targets and excludes groups of individuals.

Enterprise Rails applications aren't for beginners. But this pervasive attitude that all of Rails is beyond beginners is an abdication of responsibility.

If a newbie still can't build a Rails blog in ten minutes, let's address that. "Rails is not for beginners" is shorthand for "I can't be bothered to support beginners"

It's certainly a reputation that has managed to stick with the Rails community for a while. And we're trying to get the jerks to shut up ;-)

And while I can say that Rails is fantastic, and in my opinion, the best framework out there, I'm also going to tell you: unless someone's willing to sit down and show you, don't listen to them. That said, there are many people who _aren't_ jerks, and are more than willing to help you reimplement Google Maps. A lot of them can be found at RailsMentors.org