Though I am certain someone could do it, it is hard to dispute the connection between having choices and control over your daily work and overall job satisfaction. The people with more power to govern themselves will typically report that they are more satisfied with their jobs. This is why pairing can play a huge part both with picking who you work with and what you work on.
The difference between a 1 pair project and a 2 pair project is 3 choices vs. no choices in who you work with. You can like everyone on your team and be pleased with their work, but you can only sit side-by-side with one guy for so long. When you go up to two pairs, you suddenly have a choice that wasn’t there before, and it is there in a big way. Tired of Joe? No problem, you and Rachel haven’t paired in a while, so make that happen.
The reason people don’t need “pet projects” is because we get to pick who works on what at the top of the backlog. Yes, I have to do some grunty work, but I also get to side-step some things that I’d rather not do. More importantly, you pick what it is you work on. So now you’re doing something you chose, vs. something that was assigned to you. You as an individual have a personal investment in seeing that task through.
The work place can be filled with all kinds of challenges, and can seem oppressive if you can’t exact any control over it. By pairing and having an option to rotate, you get to pick your work and pick your coworker every single day. And choice is a great way to stay happy at work.
Ian McFarland, Principal and VP of Technology for Pivotal Labs, reprises his popular RailsConf 2010 talk. Ian describes the technical and social aspects of how Pivotal practices agile software development.
Daniel Lieberman of BitPusher says current trends in automation, reliability engineering, and cloud computing will combine and mature into a nearly-commoditized blend of operations and infrastructure. He describes ops practices during the transition.
We’re forming a Tracker User Group in the windy city, and the first meetup is scheduled for Jul 22, at the Hashrocket Chicago office.
I’ll be there to talk about the concepts and history behind Tracker, our experience with it, and will give a demo to those that are interested. It’s a great place to give feedback and ask lots of questions.
Space is limited, so RSVP soon.
jQuery.fx.off = true;
This will turn off all animations on the page and make them jump to their end state when called. There are some websites that this would be a large improvement outside of testing.
You can’t chain rake tasks – Rake is designed to emulate Make, which views running a rake task as fulfilling a requirement. This has been pretty thoroughly explained in blabs previously. If you’re having problems with rake you should take a look at thor.
For the next month or so, we will be rolling out a series of changes to various parts of the Tracker server architecture, including moving to a Memcached distributed cache for certain requests, cookie based sessions, switching from Mongrel to Passenger, splitting the very large history table, etc.
We’re doing this to improve performance, and eliminate potential scaling issues as our traffic grows. To reduce risk, we’ll introduce these changes in separate updates, once a week.
These updates will occur on Wednesdays at 7:30pm PDT (including tonight), and last under an hour each. If there are any long running migrations needed, we’ll plan them for weekends, or handle them incrementally, to avoid any extended down times.
We understand that these week night outages are inconvenient to many of you, especially in Asia. We apologize in advance, and will try and keep the updates as brief as possible.
A pivot asks if anyone has used any of the multitude of grid frameworks in a production site. Assorted developers have used and liked Blueprint, Compass and 960 grid. Blueprint was the most used, but no one had any complaints. It seems that often times people think they need a grid when really they just want a three column layout.
Another pivot reports that they are very happy after setting “paste and match style” to the default behavior for Cmd-V. The peanut gallery pointed out that you might want to paste without matching styles occasionally, and it was decided this would be an acceptable use of the mouse when it was necessary. Read more at Thaweesak
And an anecdote
The paste and match style discussion reminded another developer of a time when they were trying to compare two things pasted from terminal. They learned the hard way that there are character encoding or other issues that caused cause the diff to not include all the differences that they were looking for.