- Only keep the members who need to do something (blocking) the card on the card. Not everyone involved. After you do your part, take yourself off the card, and possibly add someone else to the card if it's their turn. It's important that all the cards with your face on it need you to do something. No false-positives.
- If you need someone's opinion on a card but they don't have to do something, just mention in a comment
- The description is the current state of the task, not a history of the evolution of the task. Comments are a history of the discussion that yields the description
- Use labels to indicate the kind of card, not state (e.g. "bug" but not "in qa"). Alternatively, have a code system in the card title. For example, we process data in batches. Batches have one to two letters to indicate client and numbers that increment. So IS42 is Internal Sales batch #42. This is nice when the label needs to be a little different each time. Instead of a label, put it at the beginning of the title.
View GitHub Profile
|# Merging Scopes|
|# The goal is to join two tables to get all the records where a scope on both|
|# side of the join is used. I used to do this with a `where()` in which I|
|# added some sql on the joined table. But, I wanted to use the existing scopes|
|# from the joining table. Turns out there's a `merge` method on a scope where|
|# you can merge with another scope without having to chain!|
|class Car < ActiveRecord::Base|