
Lucky husband of @ntduke and father of two amazing girls. Cofounder of NextView. Built some product at Ebay and learned some investing at Spark Capital
Boston, MA
Joined March 2008
- Tweets5.6K
- Following964
- Followers42.2K
- Likes10K
Super ambitious and amazing early results. Congrats @spisallyouneed and team!
Introducing SKY-001, the first Engineering World Model.
On CAD and BIM tasks, it beats GPT-6 Astra and every frontier model we tested:
-> 51-125x faster
- > 150-210x cheaper
-> Higher IOU than all frontier models
SKY-001 lets you dream a physical object before you build it.
18 months of work. Built by the team out of Maluuba's deep learning lab (acq. by @MSRResearch).
The first ‘AI General Engineer’ will be the backbone for Autonomous Manufacturing.
Rob Go retweeted
Most VCs are aiming at a bullseye on a target they can barely see.
Last year the venture industry did about 15,000 deals. A typical early-stage firm backed twelve of them. The one that cost it most is the one it never saw.
Congrats to the team at @Ultraroboticsco on their series A from terrific investors! We've been investing in physical AI for several years now, and it's a joy to be working with this team for the second time.
Robotics has a distribution problem. Today, Ultra is announcing $62M in funding to solve it, including a $50M Series A led by @hiFramework.
We believe that deployment is the bottleneck in robotics.
It’s relatively easy to make a robot look impressive in a controlled environment. It’s much harder to put a robot into the open world, make it useful, keep it running, earn the trust of the people working alongside it, and do that over and over and over again.
So that’s what we’re focusing on.
Wrote a blog post to expand on this post from a few days ago.
nextview.vc/blog/the-three-p…
It's been about a year since I wrote my post about the Existential Crisis for Seed VC's.
Some updated thoughts here on the three paths forward for seed investors.
nextview.vc/blog/the-three-p…
I directionally agree with. I think if you have 10%+ of your fund in a company, it's probably not an option.
Also, if you never write a follow-on check and never do an SPV, then it's not really an option because you never exercise it.
One misconception of this is that lower price does not = diamond in the rough. The market is actually quite efficient. A diamond in the rough can still be priced at $60M pre, if it would have otherwise been priced at $120M pre with a more consensus fact pattern.
The most promising returns are in #2. But this is harder than ever given extreme downstream funding risk, elevated entry prices, and limited exits outside of consensus winners. Funds pursuing this need to consider revamping their approach entirely. The old model won't work.
Great overview of how to think about security risk for Muse. Hilarious last post on instinct at the bottom of the thread. YOLO!
As part of testing @Muse, I quizzed it to explain to me a few things I think about when using these agents and deciding how much connections and context to give - the struggle of the Trust-Utility Curve (the more you give, the more useful it can be). xitter.cf/melodykoh/status/20262…
TLDR - there continues to be limitations around how LLMs fundamentally work and the probabilistic nature of things, and there really isn't a way to get around on context leakage or prompt injection-like attacks. However, I found Muse/Meta's willingness to be transparent in its mechanics reassuring.
A few highlights on my Q&A with Muse - see more details on the screenshots of my questions and its responses. 🧵
Q1 - you say that you will ask for my permission for actions, but how do I know this can be enforced deterministically (vs instructions in files, which are just vibes for these models)?
Most reassuring part of the answer:
"When I invoke a send tool, the runtime intercepts the call and blocks execution until you've approved it. I can't trigger the approval myself, can't see it, can't override it — the approval card is invisible to me and your decision is final. So even a compromised or injected version of me, actively trying to send without asking, hits the same wall: there is no code path where the send executes without the runtime obtaining your decision first."
Translate to non-developer speak: there's a mechanical gate that forces the model to serve up approval to the user when the action is a list of predefined "must get user approval". No vibes-bsed (good!)












