On: Beyond the Code: Mining Self-Admitted Technical De...

[hinkley]

Never ask permission to do what has to be done. If they say no, and you do it anyway, then you are being insubordinate. If you don’t do it and then point to the decision as a reason why the project is failing, then you are right, but are a failure.

[waheoo → hinkley]

And if you take too long to ship you're still a failure.

I personally force stakeholders to define sunset dates on the system / code ill be writing.

If its sunset date is never, cost of development proportional to roi approaches zero.

If the sunset date is near, cost of development gets very, very expensive.

Having that information both informs my priorities and the understanding of how long development will take / cost.

[rileymat2 → waheoo]

> If its sunset date is never, cost of development proportional to roi approaches zero.

I am not sure that is good economics, because the discount rate for the future revenue approaches 100% over extended time.

[waheoo → rileymat2]

Does it?

Not everything is monetarily cost based.

Cant recreate a space probe 30 years ago to replace the one malfunctioning now.

Cant recreate makret share gained against compeitors with stability problems.

Interesting point though, definitely ignored it til now.

Iguess the point is, everything is a trade off, and we shouldnt be acting like its either high quality or high throughput or high cost. Its somehwere in between and you get to choose depending on your contlstraints and needs.