- Tools. You should put some effort into your tools. The features to aspire to are:
- tight VCS integration
- email integration
- visual diff viewer
- inline comment annotations
- web interface is preferable
- Policy.
- Every change should be individually reviewed, before it is committed (reviewer(s) give the final OK).
- Smaller changes should be encouraged. The smaller the better, but more than 1000 lines is too big. Reviewers should request large changes to be broken up if necessary.
- A single reviewer per change is adequate, on average. 2-3 is also common.
- Reviews should also be cc'd to team and other stakeholders; unsolicited reviews/comments should be encouraged.
- A consistent code style should be enforced in reviews.
The attitude of the engineers is important, but difficult to enact. It's particularly hard when you're bootstrapping a new policy like this into your engineering culture. Although the reviewer has the final say, in reality they don't have any real power over their colleagues' actions. So they should focus on constructive, concrete issues and back off once a reasonable debate has occurred. Design reviews are important because if design issues come up in code reviews it can get ugly.
But because of Apple's proprietary copy-protection standard Fairplay, songs attained from RealNetworks' Rhapsody music service and RealPlayer music store cannot be played on Apple's iPod players.
uh, it's not fairplay that's stopping the realplayer songs from playing as such. They are both AAC, so the only sticking point would be any DRM that Real is using.
Is the article wrong, or are they saying that Real wants to license Fairplay?
Yeah, and these guys[RFG] don't know WTF they're talking about!
The RFG and IDC papers agree that linux web servers have a lower TCO than windows. This is the entire scope of the RFG paper, while it is one of five server categories in the IDC paper.
Although the numbers don't match, the conclusions don't conflict.
This may not change your mind, but here's some info you might have missed:
I probably couldn't be bothered to keep this bland cast straight in my head even if they only had one name each, but giving them all half a dozen names just made the problem exponentially worse
I'm not sure if you noticed, but the 'Dramatis Personae' section at the back of the book explains exactly this issue, and includes an index of the characters and titles.
I put it down around page 300 and haven't picked it back up in some months...
...he drops it all and starts over from the whole sodding beginning with an entirely unrelated set of characters
Maybe you should read the rest of the book before you make claims about which plots have been dropped and which characters are 'entirely unrelated'.
The cat's out of the bag, fuckwad
What does this mean? he was right, the original post was correct... and as far as I understand, the only way to use it's/its.
Slashdot Mirror
There's two aspects to make it work:
- Tools. You should put some effort into your tools. The features to aspire to are:
- tight VCS integration
- email integration
- visual diff viewer
- inline comment annotations
- web interface is preferable
- Policy.
- Every change should be individually reviewed, before it is committed (reviewer(s) give the final OK).
- Smaller changes should be encouraged. The smaller the better, but more than 1000 lines is too big. Reviewers should request large changes to be broken up if necessary.
- A single reviewer per change is adequate, on average. 2-3 is also common.
- Reviews should also be cc'd to team and other stakeholders; unsolicited reviews/comments should be encouraged.
- A consistent code style should be enforced in reviews.
The attitude of the engineers is important, but difficult to enact. It's particularly hard when you're bootstrapping a new policy like this into your engineering culture. Although the reviewer has the final say, in reality they don't have any real power over their colleagues' actions. So they should focus on constructive, concrete issues and back off once a reasonable debate has occurred. Design reviews are important because if design issues come up in code reviews it can get ugly.
http://www.bbc.co.uk/radio4/science/a bc.net.au/rn/science/ss/
http://www.
http://www.mepis.org
uh, it's not fairplay that's stopping the realplayer songs from playing as such. They are both AAC, so the only sticking point would be any DRM that Real is using. Is the article wrong, or are they saying that Real wants to license Fairplay?
you could even have intersecting spheres, so you can share your workspace with other users
Apple's Fairplay is not the same thing as Veridisc's Fairplay
paranoia, anybody?
Yeah, and these guys[RFG] don't know WTF they're talking about!
The RFG and IDC papers agree that linux web servers have a lower TCO than windows. This is the entire scope of the RFG paper, while it is one of five server categories in the IDC paper.
Although the numbers don't match, the conclusions don't conflict.
This may not change your mind, but here's some info you might have missed:
I probably couldn't be bothered to keep this bland cast straight in my head even if they only had one name each, but giving them all half a dozen names just made the problem exponentially worse
I'm not sure if you noticed, but the 'Dramatis Personae' section at the back of the book explains exactly this issue, and includes an index of the characters and titles.
I put it down around page 300 and haven't picked it back up in some months...
...he drops it all and starts over from the whole sodding beginning with an entirely unrelated set of characters
Maybe you should read the rest of the book before you make claims about which plots have been dropped and which characters are 'entirely unrelated'.
cheers
Tim
but then you would have 'stick' in both directions, and no 'slip'. How would the lense move at all?
>>...more accessable for the general population...
this was the biggest LCA yet
cheers
Tim
this is not interesting at all. I have seen microsoft adds on here before, one of them is bound to come up for some chump in this article.
You are that chump.
The cat's out of the bag, fuckwad What does this mean? he was right, the original post was correct... and as far as I understand, the only way to use it's/its.