
Akshay Dodeja
17.6K posts

Akshay Dodeja
@dodeja
CEO @terminal49, Automating Global Trade.





🇦🇪🇮🇷 UAE air defenses light up on Eid morning Iranian missiles and drones triggered sirens right as worshippers arrived for prayers. Tehran just ruined the holiest day, but said recently that Muslim countries are their allies. Source: @Osint613














Hello crustaceans! 🦞 lobsterbrew.com




@nicopreme @zocomputer Yeah I tried them but they didn't support WhatsApp.

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 ⬇️



Tesla has delayed AI6 chip production for unknown reasons, causing Samsung to put off the ramp up of 2nm manufacturing at its Taylor, Texas fab, media report, noting Tesla canceled a run of test chips (MPW: multi-project-wafer), which now faces a 6-month delay. The AI6 was to be made on Samsung’s 2nm process under a 16,000 wafers-per-month (wpm, starts) contract, while discussions on additional capacity would put the figure at 24,000wpm. The delay was revealed by AI chip designer DeepX, which was to have test chips made on the same MPW. DeepX is Samsung’s first 2nm chip client. $TSLA $SSNLF #Samsung #DeepX thelec.net/news/articleVi…

MCP sucking is a harness problem, not an MCP problem MCP unlocks behavior that is fundamentally impossible to get via CLI or APIs Bad auth, too much context usage, all get solved with an execution layer - your agent writes code to progressively discover and call tools




“MCP is dead” misses the point MCP isn’t about tools. It’s about OAuth If that seems pointless, you haven’t deployed anything beyond a demo





