"These are excellent opportunities for men ... An equal opportunity employer"

> I particularly like his definitinon of a bad programmer. (My personal record is about 12 years.)

here?

What a Programmer Does (1967) [pdf] - https://news.ycombinator.com/item?id=12568863 - Sept 2016 (45 comments)

(Reposts are fine after a year or so; links to past threads are just to satisfy extra-curious readers)

This seems true.

In my experience, these things that happened to kill programs could be considered entropy:

- New (e.g. hardware / software / code / people / focus)

- Money (e.g. actual or perceived infusion of it / actual or perceived lack of it / focus changed)

- Loss (e.g. someone or something left / was injured / died / was destroyed / was deleted / was corrupted)

And I think that if you have a system that contains risk due to entropy, then even a planned event resulting in success is entropic, e.g.:

- I plan a sunset for X software.

- There is risk of an asteroid or sudden epidemic that would thwart that plan.

- The “dice are rolled”, and the sunset happens because the asteroid and epidemic didn’t happen.

- Therefore, the planned sunset occurred due to less than 100% chance. This is still entropic.