I am developing an augmentative and alternative communication (AAC) iOS app for non-verbal adults that uses LLM-generated phrases to speed up communication. My father had throat cancer and lost the ability to speak. He was prescribed a standard grid-based AAC app but couldn't build the motor-memory needed to navigate it quickly. (https://www.speak4me.ai/)
The Vermont Food Bank, an organization I support and know well, received $9 million.
“John Sayles, CEO of the Vermont Foodbank said he received an email on Dec. 3 from a philanthropic adviser who said their client was interested in making a donation. Shortly thereafter, Sayles learned who was making the donation and how much it was for.
“And then I just spent about a day in shock,” Sayles said.
The gift is “exponentially” bigger than any other the nonprofit has received, Sayles said. The amount is the equivalent of the organization’s annual operating budget.”
We use Apache Oozie (http://oozie.apache.org/) an orchestration system for Hadoop. We don't run days-long workflows, but we run some that have over a dozen steps, and I have no reason to believe Oozie couldn't handle longer-running workflows. Oozie has facilities for handling retries based on user-defined behaviors, and because it can run shell scrips, Java apps, Spark jobs, and most anything in the Hadoop ecosystem, I've found it to be pretty easy to integrate with our other tooling. My one complaint (and it's more a complaint with YARN) is that it can be quite difficult to get your hands on logs when your workflows fail. You can get them, but it can be a real pain.
We were running Oozie on Cloudera, but are migrating to AWS, and I was pleased to find that it can be installed on an EMR cluster[1] and managed with Hue[2] which has a decent UI to administer the schedule with, and a visualization depicting the workflow DAG.