pani5ue
If your DAGs get too complicated for makefiles, it's time to rethink and restructure your DAGs
Using Textract from Amazon to do the OCR. I dump the raw json in a SQLite database.
Information extraction is trickier. I extract useful things like lines and pages, locations of lines, set up various columns and now can search the SQLite db either with python code or SQL queries.
There's of course cost for running textract OCR on AWS. There are open source solutions like Tesseract
I'm a beginner/intermediate hobby guitarist. Makes the guitar sound much better. Makes it easier to keep guitar tuned
Enterprise is often ignored by cutting edge technologies. Sounds like it could somehow eat into sharepoint confluence enterprise wikis etc. market share. of course harder to demonstrate traction but you should consider (amount of money you make + amount of money a large existing enterprise solution loses) as what makes your company valuable.
Have you considered a on-premise hosted version for the enterprise?
For mundane and painful things like requirements documents. User manuals , documentation etc.
Certainly not as cool as going consumer but enterprises have way more money than hungry writers looking for feedback.
Let me know when you're ready and/or interested and I can schedule a demo at my company. I work for a large semiconductor company.
On a chip there is now lots of redundancy to ensure chip functions correctly. This gets worse as variation at smaller geometries increases. So over margining because no one wants another floating point bug.
Design effort and cost is a huge issue too. Margins at chip companies are shrinking - design automation license costs, large runtimes and much more difficult verification process from design to fab to test.
A new programming paradigm where there is a certain probability of error can be tolerated should go a long way in making the underlying hardware much more efficient.