This is very common behavior. This is where a good manager can really help. They can recognize this is happening and then provide context.
One approach to deal with ambiguity is to write a short design doc, which writes down what you are trying to do, and all of the assumptions that you are making. If you don't understand the domain, some of your assumptions will probably be wrong. The stakeholder should be able to see that and provide guidance.
I think the AI winter was over by 2007. There was a lot of hype about machine learning and big data. The Netflix Prize for building a Recommender model launched in 2006. There was research on neural networks and deep belief networks, but they weren't as popular as they are today.
There were some interesting algorithms that came out of the contest. There was a matrix factorization algorithm that worked pretty well. Another "guy in a garage" tried to incorporate the anchoring effect into their models.
I don't think Netflix used any of the algorithms. I suspect they have more data on the user and movies than was presented in the contest.
I agree, if all of the content is garbage, then you don't need a model, you could simply pick something at random.
>For example, Sales teams are often compensated on revenue generated (outcome), but what if you did a good job (process) but didn’t hit your numbers because the market was just really bad in your vertical? A good leader will recognize this and still compensate you (i.e. hold you accountable) appropriately rather than punishing you for the outcome.
A good leader might try to keep you on the team, if they like you and you miss your numbers for a couple of quarters. From what I've seen, Sales is pretty brutal. It's quite common for Sales folks to lose their jobs, even if there are circumstances outside of their control. If they do keep you on and you don't meet your OTE, you will get paid less. In many ways their job is harder and has more risk than software engineers trying to deliver a software project on time. Which also very hard to do!
When you have a large PR like this, here's how I like to get it reviewed.
1. Give reviewers sometime to become familiar with the PR. They might not understand all parts of it, but they should have at least a cursory understanding of the PR.
2. Have a meeting where the PR is explained in front of the group of reviewers. The reviewers will understand the PR better and they can ask questions in realtime.
3. Let folks review the PR after the meeting in case they spot anything else, or think of additional questions.
Most of the time PR review is done asynchronously, but doing most of the review in the meeting can also be a decent team building exercise.
Yeah, ideally the reviewers have been in standups with you so that it isn't all new as a concept to them to begin with, or there's generally been communication that you're going to land the plans for a nuclear reactor in their work queue.
Hopefully you've been going around and around at a high level communicating back all the problems that you've hit and the design issues that emerged during exploratory surgery.
Then, you definitely want to schedule at least one meeting to go over it. Which can become several meetings, including follow-up meetings with one or two individuals to pound out some specific issue. Depends on the complexity of the nuclear reactor.
Hopefully their interest expands beyond single syllable words, otherwise the highest scores according to a cursory search are 'zizzed' (34) and 'jazzed' (32) which are probably slightly below the average for an elite player.
Zizzed and jazzed if spelled in scrabble would be worth less than 32, since only one of the zs would be worth 10 points, the rest being blank tiles which are worth zero.
Of course most good players will create more than 1 word per turn, and will lay down over multiplier tiles.
You can probably do fairly well with just single syllable words, although at a certain level not being able to get a lay down bonus will prevent you from winning.
I just ran some code over the CMU pronouncing dictionary and the longest words identified as single-syllable that are English-origin and not proper names or possessives were
The CMU dictionary thinks that "scrambled" is two syllables as a vowel ends up between the "b" and the "l" in pronunciation. Wiktionary thinks this is a syllabic l (/l̩/), which should probably be counted as a separate syllable even if it isn't considered a vowel.
Wikipedia says
> Many dialects of English may use syllabic consonants in words such as even [ˈiːvn̩], awful [ˈɔːfɫ̩] and rhythm [ˈɹɪðm̩], which English dictionaries' respelling systems usually treat as realizations of underlying sequences of schwa and a consonant (for example, /ˈiːvən/).
That's consistent with what the CMU dictionary is doing, perhaps treating /l̩/ as /əl/.
One approach to deal with ambiguity is to write a short design doc, which writes down what you are trying to do, and all of the assumptions that you are making. If you don't understand the domain, some of your assumptions will probably be wrong. The stakeholder should be able to see that and provide guidance.