If it's good to do a code review, do it more frequently. This is one of the things that happens when you do pair programming. The code is continuously being reviewed by the pair. However, when you a have a very small team you probably won't have much "promiscuous pairing" going on. Then you can do a daily team code review. It won't take much time because you're only going over today's work not a whole release. Be sure to leave enough time to refactor too!
It looks like my domain name has been picked up by some spammer's.
My domain name starts with an "early" letter and is nice and short, so it probably caught their attention.
Now, what's happening is that they are forging mail from my domain and submitting it through SMTP servers that aren't doing authentication. So now, I'm getting all sorts of bounced messages.
Seems to me that a couple of things could be done to help alleviate this sort of spamming:
When it comes to doing a code review or project review, nothing beats huddling around the projector! Even with multiple monitors you can't get more than a couple people crowding in to see the material. Since we have a big white board we can just wipe it clean and connect a projector up to one of the computers video lines. Instant big screen code review in the development area! There's still enough open whiteboard to jot notes or mark up what's being displayed. Now if I could just get the big dogs to spring for a smart board!
I think it'd be awesome to pair (or mob program) using a dual or triple projector set up on a wall!
