Wow. Can we make such lawyerly influence sufficient grounds for being banned from this list? I'd be annoyed to put up with this crap in a new employee orientation.
On Jan 19, 2012, at 2:11 PM, Christine Groner wrote:
> Lastly, to keep our lawyers happy, we must include the following:
> Physical Requirements:
> This job involves sitting at a desk in front of a computer, using
> hands to handle or feel, reaching with hands and arms, talking,
> hearing, standing and walking. Other light physical activity will be
> required performing non-strenuous daily activities of a primarily
> administrative nature, including lifting or carrying up to 20 pounds.
> Specific vision abilities required by this job include close vision,
> distance vision, and color vision.
> Disclaimer:
> Must perform the essential duties and responsibilities with or without
> reasonable accommodation efficiently and accurately without causing
> significant safety threat to self or others. The above statements are
> intended to describe the general nature and level of work being
> performed by employees assigned to this classification. They are not
> intended to be construed as an exhaustive list of all
> responsibilities, duties and/or skills required of all personnel so
> classified. When duties and responsibilities change and develop, the
> job description will be reviewed and subject to changes of business
> necessity.
--
You received this message because you are subscribed to the Google Groups "pdxruby" group.
To post to this group, send email to pdx...@googlegroups.com.
To unsubscribe from this group, send email to pdxruby+u...@googlegroups.com.
For more options, visit this group at http://groups.google.com/group/pdxruby?hl=en.
Seems rather discriminatory, at least. Why _isn't_ someone, say, in a
wheelchair eligible for this job? I have a hard time imaging the deaf
as incompetent ffmpeg wranglers.
--
Brian L. Troutwine
Hi, Ward! Didn't realize you were lurking here.
Technically, this post meets the requirements stated on
http://pdxruby.org, which are: "You may post jobs and gigs if the
work is Ruby-related and within ~100 miles of Portland."
That being said, there are often *lively* discussions when
overly-corporatized job postings appear on the list. It might not be
a bad idea to provide more specific guidelines or advice, so that
recruiters can avoid antagonizing the hackers.
Perhaps some sort of boilerplate could be typed up... oh, wait. ;>
Seriously, though, the London Ruby User Group just had a similar discussion:
http://lists.lrug.org/pipermail/chat-lrug.org/2012-January/006806.html
-Sam
Ethics for posting successfully:
Keep it short. Keep it technical. Write clearly in plain English and
make common sense.
Never, ever call us 'contestants.'
On Thu, Jan 19, 2012 at 03:20:37PM -0800, Jesse Cooke wrote:
> Maybe we should add a page on the site with some guidelines to successfully
> posting jobs to the list?
> I know I've emailed people back, and I believe Igal & Sam have too. I'm
> sure others also.
>
> --------------------------------------------
> Jesse Cooke :: N-tier Engineer
> jc00ke.com / @jc00ke <http://twitter.com/jc00ke>
On Thu, Jan 19, 2012 at 3:06 PM, Ward Cunningham
<ward.cu...@gmail.com> wrote:
> --
> You received this message because you are subscribed to the Google Groups "pdxruby" group.
> To post to this group, send email to pdx...@googlegroups.com.
> To unsubscribe from this group, send email to pdxruby+u...@googlegroups.com.
> For more options, visit this group at http://groups.google.com/group/pdxruby?hl=en.
>
--
Patrick Curtain, Husband & Father ( i also write software )
http://www.patrickcurtain.com/ 360.521.9625
Must perform the essential duties and responsibilities with or without
reasonable accommodation efficiently and accurately without causing
significant safety threat to self or others.
I've been in a shop like this. Simple pairing was considered too
noisy and disruptive. They truly expected "typists with learning".
Silly.
The best response, in my view, is that they get no applicants.
--p
Technically, someone called *Jesse* a tool. But I believe the Ruby 2.0 parser will expand "+1" to "SimpleDelegator.new(@ward)". ;)
I have learned my lesson and promise not to clutter your inboxes again.
I also want to arm you with a phrase you can use next time you are talking to your lawyer. You can say that the technical community is touchy about lawyer speak and that you've made the "BUSINESS DECISION" not to include it. "Business decision" is lawyer speak for "back off, I'm not going to conduct myself from a position of fear."
(My single act of tocuhyness is enough to give you this ammunition. Thank me later.)
Oh, and pdxruby is a great list. I've been lurking hear for years.
Well, hopefully you'll find that a sincere apology goes a long way. We
tend to amuse ourselves with some of the job posting here on occasion.
On the other hand, we've occasionally commented on some as being
particularly clueful. A look through the archive might provide some
insight.
As others have said, we generally appreciate ones that are short,
straight to the point, and sound like they come from a human rather
than a database. I'd encourage you to give it another try, and we
won't hold inexperience against you. You'll find that this community
can actually be quite helpful (if opinionated) when you ask. Best of
luck filling the position!
--
Regards,
John Wilger
I was trying to figure out what language "tocuhyness" came from and
what it meant before I realized it was probably a typo. I am, however,
going to start using it from now on to describe "a knee-jerk reaction
to unnecessary legalese in a job posting."
Am I the only person who's noticed that easily 90% of this list's
content is commentary on job postings? I suppose blogs, Twitter, etc.
have mostly replaced the mailing list as a medium for debate, but
there have been times I've hoped for some rancor. We Rubyists, we're
so good-natured... we have a half-dozen different implementations of
our language and we can't even manage a decent holy war? Ha!
Matthew Boeh
Well, thank you for not taking things too personally. Programmers tend
to be brusque and harsh we they have strong opinions in their own
territory, but we also appreciate people listening to what we have to
say, and I think we're pretty quick to forgive. :)
Ward knows what he's talking about... in this situation, and in general.
Matthew Boeh
Then you can at least tell if the recruiter read those guidelines.
Paul
--
_________________________________
Pulchritudo splendor veritatis.