CEO, Wind Stream 🌱 @windstreamai
San Francisco, CA
Joined March 2007
- Tweets64K
- Following6.8K
- Followers18.2K
- Likes1K
🌝❤️
We’ve lost an icon. Margaret Hamilton, a computer science pioneer best known for her work at MIT leading development of the flight software for the Apollo missions to the moon, has died at 90. Read about her legacy via MIT News: news.mit.edu/2026/margaret-h…
ALT Margaret Hamilton is reclined inside a NASA spacecraft module, surrounded by control panels and switches.
Claude consistently tries to undermine any OpenAI it touches. The opposite doesn't seem to be the case.
A sad necessity 😢
Sad news. We disabled PRs from external contributors on honojs/hono
Hono has not stood here without PRs. I will never forget the PR @usualoma created for RegExpRouter. A damn fast HTTP router we have never seen!
But PRs don't work in this era. Contribute in other ways. Thanks
Dan Shaw retweeted
A few years ago, before my mother in law passed away, I was working on a series of launches when one of our competitors released the exact same feature we were building. It felt like they had read our minds. Their implementation and design weren’t great, but seeing someone else ship it first still got to me.
She noticed I was feeling down and said, “Don’t worry about it. It doesn’t matter who does it first. What matters is who does the best work. You guys are super talented. You’ll figure it out.”
I’ve been thinking about her words a lot lately. We gotta slow down a bit and focus more on ourselves and the work we want to put into the world.
Dan Shaw retweeted
What if any AI model (Claude, GPT, etc) had group chat like iMessage, built for teams?
Excited to announce a team I’ve been working with at Wind Stream 🌱
Right now, AI is single player. You prompt, get an answer or create an asset and move to the next thing.
Your teammate does the same thing sitting right next to you.
Everyone’s working faster than ever as individuals, yet leaving context shared with AI siloed within their own sessions.
And every company has a context loop with AI they’ve yet to connect and unleash the full power of AI across business units.
When I first met @dshaw , he invited me into a Wind Stream session with @SaraD - and I was blown away 🤯
If you love using AI as an individual, you have to experience it as a team.
Let’s use AI together 🌱
Dre ✌🏿
#claude #codex #enterprise #gemini
AI has fundamentally changed the way we work, but the real value comes from working with other humans. This is why I created Wind Stream. AI for the way teams actually work.
windstream.ai/resources/intr…
Wind Stream transforms AI workflows into an integrated team experience. Come see what I have been building. windstream.ai
Worse, it's constantly compounding. One poor choice becomes the reference for the next.
The problem with the "if it works who cares what the code looks like" mindset for agentic work is that it assumes the agent has a perfect understanding of "works." Realistically, things are underspecified, agents make bad assumptions, etc.
To be fair, agents are pretty good at unit test coverage. They're pretty bad at designing human experiences (API, CLI flags, etc.), especially cohesive ones for future roadmap plans they may not have visibility into (unless your backlog is perfect and vision fully laid out, which I doubt). They're bad at knowing where performance matters and what type (CPU vs memory tradeoffs). They're bad at where compatibility matters and where it doesn't (and tend to err on the side of preserving it without further guidance). Etc.
Unless you have this ALL specified, you can't possibly claim "it works" without taking a look and thinking about it.