I got a $1500 quote to replace a stuck thermostat in my car from my local mechanic. After some Youtubing I was able to replace the part myself with $150 in parts.
I got a $5000 quote to fix my AC 2 summers ago and no amount of Youtube was able to help me DIY a fix.
Maybe in the long term there will be more HVAC techs than auto mechanics. Somehow I don't think that's likely.
There are two paths to KG generation today and both are problematic in their own ways.
1. Natural Language Processing (NLP)
2. LLM
NLP is fast but requires a model that is trained on an ontology that works with your data. Once you do, it’s a matter of simply feeling the model your bazillion CSVs and PDFs.
LLMs are slow but way easier to start as ontologies can be generated on the fly. This is a double edged sword however as LLMs have a tendency to lose fidelity and consistency on edge naming.
I work in NLP, which is the most used in practice as it’s far more consistent and explainable in very large corpora. But the difficulty in starting a fresh ontology dead ends many projects.
I agree with you but the only time execs were held personally responsible that I can remember is Enron and that was on insider trading charges. There is so much plausible deniability and near unlimited appeals built into the system that it would take mountains of evidence and several hundred Lina Khans for an actually responsible executive to be tried for something like this.
I joined my current company to work on Growth. I was added to Gitlab, and for the first 3 months I pushed all my commits as MRs that my manager reviewed and merged into main. Standard procedure.
One day I needed to get a hotfix out to prod STAT. I pinged my manager to accept the MR and explained all the testing I've done. He said I could just accept it myself if I wanted it up now.
Turns out I've had the permission to push to prod since day one. The only red tape I had to cross was my own confidence.
This is awesome. I built a real time whiteboarding app for teachers over 10 years ago on the backbone of the original Firebase service.
It was so fast I was able to build basic collision physics of letter tiles and have their positions sync to multiple clients at once. What a shame to be killed by Google.
I haven't had a need for real time databasing since, but this is inspiring me to build another collaborative app.
I wrote a tiny self-hosted price tracker that doesn't require a server to run.
It idles as an automator calendar alarm and runs on schedule like a calendar event. When a price drop is detected, it displays a notification using osascript.
When my macbook is asleep, it waits to check the price on wake.
The only input required is the URL of the product page. You can include a target price if you like.
