Slashdot is powered by your submissions, so send in your scoop


Forgot your password?
For the out-of-band Slashdot experience (mostly headlines), follow us on Twitter, or Facebook. ×

Comment: More complex projects (Score 1) 126 126

We do pair programming for larger projects without many explicit specs. These projects require you to 'think up' use cases and requirements on the fly to ensure that your code is sufficient, complete and valid. For instance we created a replacement for a parser of complex documents that had to get classified. We had a coder with strong domain knowledge and a strong coder. Not sure what to do when n > 2.

Comment: Re:No one wins (Score 2) 124 124

I rewrote that for you:

Announcing to the world that you've been infiltrated by [major unknown party] is a decision that must be weighed by some enormous number of calculated steps.

If you're correct, you have risk

If you're wrong, you have risk

The only winning move is not to play.

Comment: Re:Compactness and Readability (Score 1) 298 298

What is missing is the word 'design'. You may comment why you made a design (or write a paper on it). You may understand the design by reading the code. If you don't it is either too complex (because there is a possibility to write the same functionality with the same complexity with easier-to-read code) or you need to explain the design for it.

The only thing necessary for the triumph of evil is for good men to do nothing. - Edmund Burke