For all the harsh words you posted without evidence, thankfully you've at least admitted you don't understand much.
Your premise is that cryptocurrency is not "spendable currency" which is simply false. I pay people in hyperinflationary environments in cryptocurrency variants with low transaction costs and fast speed, and they in turn directly spend it on physical goods like food.
Eventually I realized that Haskell code is slow to write, hard to reason about efficiency, lazy evaluation sucks for most things, and most importantly Haskell is hard to read by others. Going on Hoogle to look up some package and seeing some abandoned doctoral thesis used by nobody where the only documentation is types becomes exhausting after a while.
Go is now my favorite language.
Sounds like you're not a team player who wants to be promoted to better support your family. /s
The business is an American manufacturer that added capacity to manufacture PPE to make up for the lack of Chinese supply. Since we were supplying direct to the market, the prices of the PPE were in-market from before COVID times, or cheaper. We weren't out to make a killing, just to fill up some manufacturing time and help folks out. We had the equipment, the people, the facility.
However, we didn't have a great way to reach people who needed it - healthcare was not our normal industry - so we decided to put it up on Adwords.
Within 24 hours, the account was suspended. We appealed it (thinking it must have been a mistake), and a month later, they told us they reviewed it and maintained the suspension. We told them we were only promoting PPE to help people in health care find supply and they didn't care. We've never had suspension issues before.
The whole experience left a very negative taste for Google. With their extreme dominance in market share for advertising, they no longer need to cater to customers' needs. (Maybe they care if you're a multimillion dollar customer, but certainly not if you're an everyday SME manfuacturer.) And there's not a lot of alternatives to turn to for that type of advertising. There was no recourse, no discussion, no reasoning. Just the Google blank wall.
We wound up manufacturing lots of it anyway to hospitals in need, but Google actively tried to stop distribution of American-made PPE during the pandemic.
Imagine that our interview goes like this:
Q: Can you implement a red-black tree?
A: I don't know. My Ph.D. is not in CS and I never actually seem to get around to reading the copies of Knuth and CLRS that I optimistically keep on my shelf. Nobody really wants to pay me to read about trees. So mostly I just use other people's trees, particularly the ones that are hiding inside Postgres and MySQL.
It would be fun to try to figure out how to implement a binary tree by asking you twenty questions -- it's one of my favorite party games -- but it will take a bit of time, and I'm in an interview and feeling nervous, so I'm not sure my odds of success are that high.
I did read on Wikipedia the other day that operations on balanced binary trees are O(log N) which makes intuitive mathematical sense, given that a branched structure with n levels will have 2^n leaves. So I guess balanced trees are pretty fast.
What do you do next?
I presume that, given that I've failed to answer the specific question, and demonstrated a degree of "slickness" and "force of personality" in the process, that you will ask me if I have any questions, shake my hand, send me out the door, inform your colleagues (including the one who referred me to your company) that I'm a NO HIRE because I couldn't remember the algorithm for constructing a red/black tree, and send me a polite rejection letter the next day?
Perhaps that strategy would have the virtue of being fair. But could you please get it over with during the phone screen? Better yet, could you make sure your recruiters never even email people who don't explicitly advertise CS degrees? Because I'd hate for you to waste a single minute thinking about me, and vice versa. Time is precious. If I find enough of it, I might even get around to reading Knuth!
And also Ackoff's talks on Systems Thinking:
2. Recursion, not just in programming, but in other parts of nature.
3. Memory and social size approximations, such as memory chunking in seven plus or minus two, and Dunbar's number.