If you're building AI agents, the first thing you have to do is stop reading tweets and start reading papers, docs from model labs, and a few blogs. I feel like my brain has become context overloaded from reading tweets about agents. :|
We've raised $6.5M to kill vector databases.
Every system today retrieves context the same way: vector search that stores everything as flat embeddings and returns whatever "feels" closest.
Similar, sure. Relevant? Almost never.
Embeddings can’t tell a Q3 renewal clause from a Q1 termination notice if the language is close enough.
A friend of mine asked his AI about a contract last week, and it returned a detailed, perfectly crafted answer pulled from a completely different client’s file.
Once you’re dealing with 10M+ documents, these mix-ups happen all the time.
VectorDB accuracy goes to shit.
We built @hydra_db for exactly this.
HydraDB builds an ontology-first context graph over your data, maps relationships between entities, understands the 'why' behind documents, and tracks how information evolves over time.
So when you ask about 'Apple,' it knows you mean the company you're serving as a customer. Not the fruit.
Even when a vector DB's similarity score says 0.94.
More below ⬇️
🚨Did you see what Karpathy just said? Stop everything and read this.
3 years ago this man was teaching the world how to build neural networks from scratch.. Stanford lectures. YouTube tutorials.. "Here's how to write a GPT from zero."
> Now he's saying don't write code at all. Just manage the agents that write it for you.
The same guy who literally taught a generation of engineers how to code is now telling them their job is to sit in a command center and babysit AI workers. He compared it to a tmux grid. Yuchen Jin in the replies compared it to StarCraft.
These people are not joking. They're designing a future where "software engineer" means "guy who watches 12 AI agents on 6 monitors and makes sure none of them crashed."
And then.. AND THEN.. he casually says you'll be able to fork entire companies. Not code. Companies. Copy-paste someone's whole operation like it's an open source repo..
The man who mass produced software engineers just mass produced CEOs. And he did it in a tweet.
If you spent the last 5 years grinding LeetCode and building a résumé to get into FAANG, I genuinely don't know what to tell you right now.
The guy who wrote the playbook just burned it.
If there are engineers that have been affected by the layoffs that want to help rebuild the technical infrastructure of supply chain from the ground up, @getburnt_ai is hiring.
We believe that ERPs, the system of record for supply chain companies, will be a relic of the past and were ushering the industry into the future.
If working on hard problems that affect how the world moves excites you, reach out.
Cluely is cooked. So is InterviewCoder. UltraCode too. Along with hundreds of "invisible cheating" tools.
We built the HackerRank App to block this.
Now, I know what you may be thinking as a developer: how do I trust the app?
It blocks plagiarism tools, screen sharing, tab switching, external apps, and more, all while still giving developers an insanely great experience.
Companies can even enable an AI assistant directly inside the test, so candidates do not have to rely on external references at all.
"Cheating" might feel cool. But losing a job to someone who only got that because they played unfairly is not.
Link below to learn more.
Burnt (@getburnt_ai) builds AI agents for food distributors, automating entire job functions like order entry so sales and customer service teams focus on growth, not data entry.
https://t.co/yNUCYghyLg
Congrats on the launch, @joseph_jacob13, @rheakarimpanal, and @tweetchanshan!