The Stack Overflow podcast is back! Listen to an interview with our new CEO.
    Post Unlocked by yannis
    Notice removed Content dispute by yannis
    Post Locked by Thomas Owens
    Notice added Content dispute by Thomas Owens
10 Rollback to Revision 7
source | link
  1. Are there any additional costs or pitfalls related to the suggestion I have proposed.
  2. Based on experience (the criterion set out in the "Good Subjective vs. Bad Subjective" discussion), can you provide alternative views of this design problem or alternative ideas that have solved the problem well in past instances.
  3. Can you provide facts or widely-cited sources to bolster any thoughts on (1) or (2) above, to foster a more thorough answer of the proposed ideas (please do not merely post answers that are purely references to outside sources since this question is not a request for references).

Are there any significant pitfalls that I am failing to realize about the proposed idea regarding don't-repeat-yourself vs. build-in-flexibility trade-offs in parameter file design?

  1. Are there any additional costs or pitfalls related to the suggestion I have proposed.
  2. Based on experience (the criterion set out in the "Good Subjective vs. Bad Subjective" discussion), can you provide alternative views of this design problem or alternative ideas that have solved the problem well in past instances.
  3. Can you provide facts or widely-cited sources to bolster any thoughts on (1) or (2) above, to foster a more thorough answer of the proposed ideas (please do not merely post answers that are purely references to outside sources since this question is not a request for references).

Are there any significant pitfalls that I am failing to realize about the proposed idea regarding don't-repeat-yourself vs. build-in-flexibility trade-offs in parameter file design?

9 added 63 characters in body
source | link
  1. Are there any additional costs or pitfalls related to the suggestion I have proposed.
  2. Based on experience (the criterion set out in the "Good Subjective vs. Bad Subjective" discussion), can you provide alternative views of this design problem or alternative ideas that have solved the problem well in past instances.
  3. Can you provide facts or widely-cited sources to bolster any thoughts on (1) or (2) above, to foster a more thorough discussionanswer of the proposed ideas (please do not merely post answers that are purely references to outside sources since this question is not a request for references).
  1. Are there any additional costs or pitfalls related to the suggestion I have proposed.
  2. Based on experience (the criterion set out in the "Good Subjective vs. Bad Subjective" discussion), can you provide alternative views of this design problem or alternative ideas that have solved the problem well in past instances.
  3. Can you provide widely-cited sources to bolster any thoughts on (1) or (2) above, to foster a more thorough discussion of proposed ideas (please do not merely post answers that are purely references to outside sources).
  1. Are there any additional costs or pitfalls related to the suggestion I have proposed.
  2. Based on experience (the criterion set out in the "Good Subjective vs. Bad Subjective" discussion), can you provide alternative views of this design problem or alternative ideas that have solved the problem well in past instances.
  3. Can you provide facts or widely-cited sources to bolster any thoughts on (1) or (2) above, to foster a more thorough answer of the proposed ideas (please do not merely post answers that are purely references to outside sources since this question is not a request for references).
8 Rollback to Revision 6
source | link

Are there any significant pitfalls that I am failing to realize about the proposed idea regarding don't-repeat-yourself vs. build-in-flexibility trade-offs in parameter file design?

  1. Are there any additional costs or pitfalls related to the suggestion I have proposed.
  2. Based on experience (the criterion set out in the "Good Subjective vs. Bad Subjective" discussion), can you provide alternative views of this design problem or alternative ideas that have solved the problem well in past instances.
  3. Can you provide widely-cited sources to bolster any thoughts on (1) or (2) above, to foster a more thorough discussion of proposed ideas (please do not merely post answers that are purely references to outside sources).

Are there any significant pitfalls that I am failing to realize about the proposed idea regarding don't-repeat-yourself vs. build-in-flexibility trade-offs in parameter file design?

  1. Are there any additional costs or pitfalls related to the suggestion I have proposed.
  2. Based on experience (the criterion set out in the "Good Subjective vs. Bad Subjective" discussion), can you provide alternative views of this design problem or alternative ideas that have solved the problem well in past instances.
  3. Can you provide widely-cited sources to bolster any thoughts on (1) or (2) above, to foster a more thorough discussion of proposed ideas (please do not merely post answers that are purely references to outside sources).
7 Rollback to Revision 4
source | link
6 added 264 characters in body
source | link
5 Rollback to Revision 1
source | link
4 Rollback to Revision 2
source | link
3 Rollback to Revision 1
source | link
2 shopping /off (http://blog.stackoverflow.com/2010/11/qa-is-hard-lets-go-shopping/)
source | link
1
source | link