3 ms·

Deleted not to please downvoters.

genezeta 8y ago
The point is not whether it is correct and necessary, but that its existence makes the argument that it is indeed so. What you mention is actually the insight that "it may not be". But you reach that idea _against_ the argument its presence is making. That is, you find some code. Its presence says "I'm here for a reason", your answer of "maybe it's just because..." comes as, precisely, an _answer_ to that argument. Neither the argument itself nor your answer are necessarily and always correct. This doesn't argue that point, just that the presence of a piece of code makes such an statement.
- deleted 8y ago
  [deleted]
codetrotter 8y ago
The article explains what is meant. > We know that code represents effort expended, and we are very motivated to preserve the value of this effort. And, unfortunately, the sad truth is that the more complicated and incomprehensible the code, i.e. the deeper the investment in creating it, the more we feel pressure to retain it (the "sunk cost fallacy"). It's as if our unconscious tell us "Goodness, that's so confusing, it must have taken ages to get right. Surely it's really, really important. It would be a sin to let all that effort go to waste."
- your-nanny 8y ago
  I think it is a mistake to call this a sunk cost fallacy. the other stuff is true, but it's not the same thing as the sunk cost fallacy
nullisnullish 8y ago
I really enjoyed you insighful comment. I can't understand all those furious downvoters. Perhaps they are a bad abstraction.
- bothareright 8y ago
  I really agree with both of you.
  - bothareright 8y ago
    I should guess hamandchess and trufa are very young people, that are beginning in paid software. This explain they overvalue experienced programmers blogs.
    - Pica_soO 8y ago
      The only thing experienced programmers truely value is profiling- write it, run it, measure it. Advice is nice and all, but at the end of the day, even that new method to write code, gets to perform on the profiling table of your manager. OO ? Use it, run it against procedural or functional approach, measure it, decide. Everything else is politics, religion and that one irresponsible guy who gets high on new things and away with it somehow, while touring companys.

The point is not whether it is correct and necessary, but that its existence makes the argument that it is indeed so. What you mention is actually the insight that "it may not be". But you reach that idea _against_ the argument its presence is making. That is, you find some code. Its presence says "I'm here for a reason", your answer of "maybe it's just because..." comes as, precisely, an _answer_ to that argument. Neither the argument itself nor your answer are necessarily and always correct. This doesn't argue that point, just that the presence of a piece of code makes such an statement.

deleted 8y ago
[deleted]

codetrotter 8y ago

The article explains what is meant. > We know that code represents effort expended, and we are very motivated to preserve the value of this effort. And, unfortunately, the sad truth is that the more complicated and incomprehensible the code, i.e. the deeper the investment in creating it, the more we feel pressure to retain it (the "sunk cost fallacy"). It's as if our unconscious tell us "Goodness, that's so confusing, it must have taken ages to get right. Surely it's really, really important. It would be a sin to let all that effort go to waste."

your-nanny 8y ago
I think it is a mistake to call this a sunk cost fallacy. the other stuff is true, but it's not the same thing as the sunk cost fallacy

nullisnullish 8y ago

I really enjoyed you insighful comment. I can't understand all those furious downvoters. Perhaps they are a bad abstraction.

bothareright 8y ago
I really agree with both of you.
- bothareright 8y ago
  I should guess hamandchess and trufa are very young people, that are beginning in paid software. This explain they overvalue experienced programmers blogs.
  - Pica_soO 8y ago
    The only thing experienced programmers truely value is profiling- write it, run it, measure it. Advice is nice and all, but at the end of the day, even that new method to write code, gets to perform on the profiling table of your manager. OO ? Use it, run it against procedural or functional approach, measure it, decide. Everything else is politics, religion and that one irresponsible guy who gets high on new things and away with it somehow, while touring companys.