The scenarios you’ve posed doesn’t make candidate 2 any less replaceable. Maybe candidate 1 is needed for whatever advanced AI the dating app uses, but there’s many non-foreign options for the function candidate 2 is performing at ImportantCorp.
Yes, I think what the parent comment intended to say was that the UI for the CT scan machine is more valuable for the society (and hence candidate 2 should be given preference) than the fancy AI algorithm that goes into the dating app, even if it would actually take an ETH grad to come up with it.
Yes, super subjective, but that's the point - it would be difficult to account for these things in the law.
That point hasn’t been hit yet. Discouraging people from learning programming because you anticipate that point to come soon is unfortunate coming from a manager of programmers. Regardless of job opportunities, which I disagree with but is beside the point, being able to program increasingly allows people to create value and bring ideas to existence.
If your only reason to hate a language is that it's making improvements (that you can't/won't keep up with), it would seem that language is doing something right
It's not that it's improving, it's that it's changing in every direction at light speed, and if you say went on holiday for a month offline when you come back the odds that you find the syntax and the ecosystem substantially different is very high. And whether all or most of these changes are indeed improving anything is doubtful. I personally can't follow JS anymore, it's a storm of not-so-news from every direction.
Since ES6/2015 the changes have been pretty minimal, so I disagree with your assertion. Since 2015 I find that async functions is probably the most alien addition... and the handful of others that are significant are mostly ignored or very natural extensions.
The shift from callbacks to promises is kind of alien, but frankly that was started well before 2015 even. The .babelrc I use for node projects is pretty simple as well, here's one I use for an AWS Lambda build...
So that's literally 3 things that aren't in spec yet, and a couple that work around the runtime not having them. Most of what's going in is already in, or relatively well established and on the way.
Now, you do have to include a lot more if you want IE11 support, but hey, that's a different thing. I'm not sure what exactly you're having a trouble wrapping your head around.
Passion implies things other than working longer than everyone else. For example, people passionate about programming often are better at debugging in those 8 hours than someone who wants to just get out.
Also, I don't understand the use of images here. Your first one is basically the equivalent of a cliche speech starting with, "The Marriam-Webster dictionary defines passion as..."
> Passion implies things other than working longer than everyone else.
Not to a lot of managers and bosses, it doesn't.
My team has weekly rewards for the people that work the most hours. Several people on the team regularly claim to put in 60-80 hours.
Personally, I feel that those same people are making the work environment worse. One of them in particular has created over 200 Bamboo build plans (and the corresponding deployment plans to 7+ environments). It's an unmaintainable mess with little-to-no logic involved. None of it is re-usable -- hence why there are over 200 build plans.
That guy gets praise several times a day for how hard he works.
The bosses don't care about how much passion (in our sense of the word) their employees have. They care about how much passion (in the "work 80 hours a week" sense of the word) their employees have.
"To me a phone is a poor man's computer that you have to use when you are on the road, but if you are in front of your desk, there is no reason you should be forced to use an inferior input interface to interact with your accounts when you have a keyboard and a trackpad in front of you."
