260 karma · joined April 23, 2009
That one word, "setting," puts her squarely in bullshitter territory. The obvious and honest word is "prison". But that's too dark a color for the painting she's holding up for us.
Unix Systems Administrator
Responsibilities:
• Maintain internal and external Linux/Mac/Windows systems in a highly automated/repeatable way.
• Improve and maintain service and performance monitoring infrastructure.
• Provide infrastructure support to our development team through the product development and deployment lifecycle.
• Monitor and improve system security.
• Provide occasional support to desktop users.
Desired skills and experience:
• SAGE Level II/III skill set. ( http://www.sage.org/field/jobs-descriptions.html )
• 3+ years systems administration experience.
• Experience with Puppet or other configuration management tools.
• Understands the importance of virtualization combined with automated provisioning & maintenance.
• Demonstrated ability and desire to learn continuously.
• A bias towards open source tools.
• A love of command lines.
• Experience with PostgreSQL a plus.
• Bachelor of Science in Computer Science, Computer Engineering, or equivalent experience.
We value people, teamwork, innovation, diversity, and a healthy life balance, with an overriding dedication to quality in everything we do.
If this sounds like you, we'd love to hear from you. Send your resume to us at work@renewfund.com.
I guess Facebook just further validated this mobile multimedia medium.
Is this different than how the count works in states whose ballots are delivered via volunteers with ballot boxes?
Here's a sample:
Feature: Manage Credentials
Background:
Given I am signed in as a superuser
And there are 3 credentials
Scenario: Listing Credentials
When I view the list of credentials
Then I should see all 3 credentials in the list
When I add a 4th credential
And I view the list of credentials
Then I should see all 4 credentials in the list
When I change the name of the 1st credential
And I view the list of credentials
Then I should see that the 1st credential's name has been changed
When I delete the 2nd credential
Then I should see all credentials except the deleted onePut another way, if food producing acreage is the limiting factor for humans then as omnivores we may grow for 150,000 generations, as herbivores we may make it to 150,005 generations. Either way, growth will have to stop and we will have wiped out massive numbers of other species.
# bad
email_with_name = user.name + ' <' + user.email + '>'
# good
email_with_name = "#{user.name} <#{user.email}>"
# better
email_with_name = "%s <%s>" % [user.name, user.email]Regarding diversity, I actually think we're pretty diverse. Our 8 developers include:
1 Indian, 1 Palestinian
1 woman
2 overweight but not obese
2 introverts, 1 strong extrovert, 3 mild extroverts
1 M.A., 1 M.S. working on his PhD. 2 high school drop outs.
2 Textmate, 6 vim
1 under age 30, 3 over age 40
1 ex-con, 1 former jazz musician
4 married with children
3 prefer dogs, 4 cats
Apparently, though, we all like to mountain climb.
Our team has a high number of extraverts, but the introverts seem just as happy. We have no surly curmudgeons.
When I hired on, I was surprised that so many people rode bikes to work. And when I proposed climbing a local mountain to one similarly outdoorsy co-worker, I was surprised that the whole team was interested. 10 out of the 12 in the office either did the warm-up climb or actually camped out overnight and completed the larger climb (Mt St. Helens). I found this amount of shared lifestyle/outside-interests to be unique among places I've worked. I'm certain we weren't hired because of these interests, but it seems to have worked out that we share a lot of them.
Last Friday our team presented some of our dev proceses to the local agile group. We had 5 devs and a product person there. Someone observed that our team seems to have really good personal chemistry and we all agreed. We chalked it up to careful hiring. If you wouldn't function well with our set-up, we probably wouldn't offer you a job.
Regarding definitions of "in the zone", mine wouldn't include a pair in a good rhythm. Being in the zone, to me, evokes a lone programmer writing lots of code while holding complex mental models in his/her head for hours at a time. It's a pleasurable feeling for most of us with a bent for logic and problem solving, but my experience is that it doesn't always produce the best code.
* spelling edit
What I was attempting to describe is the mindset our team currently has, not what yours should have.
Our particular team of 8 devs is happy and productive with it. I do understand that this approach could be less than ideal for a different team, or the same team working on projects of a different nature.
"Disruptions" are conversations where ideas and implementations are fleshed out. That's the hard work. Coding quietly means you're doing something so trivial that pairing would be silly.
I really believe this dev culture produces fewer defects and makes the team more responsive since so much knowledge is shared.
We're protected from the busy road and the grocery store parking lot by elevation; we're 50 ft below either. We can hear the highway, but I only notice it when the din is missing when we visit friends in the country!
I have no idea if I'm healthier or will live longer or have more sex or my hair is growing back, but I do prefer it to sitting down.