4 ms·

That's a good perspective. What's really lacking from so many of the "bad" comments is the context of the original comment. If you drop the context of someone u

That's a good perspective. What's really lacking from so many of the "bad" comments is the context of the original comment. If you drop the context of someone using Python to process a moderate amount of text on a large, non-real-time system, then project your own context where it doesn't work, then sure python is not a good choice. If you can't agree on a basic context, or choose to force a context on them, then there's no compromise. Like in your teacher's example, you can't compromise between memory and cpu if you have no idea which you care about more. They're mostly of the format "I like spoons because they can pick up liquids!", then the reply is "no forks are much better because they have tines to stab with!", without anyone saying if they want to eat soup or spaghetti.

zelias 7y ago
This is spot on. As the old saying goes, "you can't have an argument about euthanasia with someone who thinks euthanasia is a musical group."
- ourmandave 7y ago
  Every reviewer of their performances says, "They're killing it!"
SkyBelow 7y ago
>If you drop the context of someone using Python to process a moderate amount of text on a large, non-real-time system, then project your own context where it doesn't work, then sure python is not a good choice. If you can't agree on a basic context, or choose to force a context on them, then there's no compromise. There may also be past traumatic experiences that are sought to be avoided. How many times does it take for some management to grab your local working python solution, slam it into production, and then complain when it falls apart? Even with a single such instance, you begin to look at things with the view that the context may be shifted away from the intention. In such a situation, you are fully aware the context is locally with 1,000 files and not in some production environment with some 1,000,000,000, but you are rejecting the notion that those contexts can be so completely separated because a past instance showed such separations can be undone. Once bitten twice shy.
- jkoudys 7y ago
  That's the eternal struggle in software engineering, I'm afraid. In my experience, there's no product that performs better with a more complete feature-set than the MVP from two years ago that exists only in the CEOs imagination, and was never really used by anyone. It takes a lot of knowledge and experience to understand why the very good solution that I run off my laptop once every week or two isn't at all the same as one that could handle hundreds of thousands of non-experts running it every minute.

zelias 7y ago

This is spot on. As the old saying goes, "you can't have an argument about euthanasia with someone who thinks euthanasia is a musical group."

ourmandave 7y ago
Every reviewer of their performances says, "They're killing it!"

SkyBelow 7y ago

>If you drop the context of someone using Python to process a moderate amount of text on a large, non-real-time system, then project your own context where it doesn't work, then sure python is not a good choice. If you can't agree on a basic context, or choose to force a context on them, then there's no compromise. There may also be past traumatic experiences that are sought to be avoided. How many times does it take for some management to grab your local working python solution, slam it into production, and then complain when it falls apart? Even with a single such instance, you begin to look at things with the view that the context may be shifted away from the intention. In such a situation, you are fully aware the context is locally with 1,000 files and not in some production environment with some 1,000,000,000, but you are rejecting the notion that those contexts can be so completely separated because a past instance showed such separations can be undone. Once bitten twice shy.

jkoudys 7y ago
That's the eternal struggle in software engineering, I'm afraid. In my experience, there's no product that performs better with a more complete feature-set than the MVP from two years ago that exists only in the CEOs imagination, and was never really used by anyone. It takes a lot of knowledge and experience to understand why the very good solution that I run off my laptop once every week or two isn't at all the same as one that could handle hundreds of thousands of non-experts running it every minute.