In the real world there is no If You Build It They Will Come, you've got to get the word out

>> "costs way too much"

>> "It's not like chat is a hard problem"

Surely these statements can't all be true. Since Slack is expensive and has little competition, I think chat is a harder problem than you think.

Also a huge number of spacey contemporary works like A Mote in God's Eye, Rendezvous with Rama, Dune, Ringworld...

Self-driving taxis have a high floor for 'making the product worse' because the car fundamentally has to drive itself.

Then find all words with 7 unique letters, then get the unique set of letter sets. These are your valid puzzles times 7 for each selection of a center letter.

Construct a trie of your dictionary. For each letter of each puzzle, walk the trie using only the puzzle letters. When you find a word, if it used the center letter, add to list.

In practice it's log(n) for size of dictionary.

Consider the following table of medical surgeries: date,physician_name, surgery_name,success.

"What are the top 10 most common surgeries?" - easy in bash

"Who are the top physicians (% success) in the last year for those surgeries?" - still easy in bash

"Which surgeries are most affected by physician experience?" - very hard in bash, requires calculating for every surgery how many times that physician had performed that surgery on that day, then compare low and high experience outcomes.

A researcher might see a smooth continuum of increasingly complex questions, but there are huge jumps in computational complexity. At 50gb dataset might be 'bigger' than a 2tb one if you are asking tough questions.

It's easier for a business to say "we use Spark for data processing", than "we build bespoke processing engines on a case by case basis".

Hoping they do it for April 1st one year.

I remember this getting a lot of buzz at the time, but few orgs are at the level of sophistication to implement chaos testing effectively.

Companies all want a robust DR strategy, but most outages are self-inflicted and time spent on DR would be better spent improving DX, testing, deployment and rollback.