vu1nss🏴‍☠️☢️☠️

This 😅😱👇🏼

@alliekmiller #4 is so true, I call it the hybrid user. But yeah, those users with a niche feature set for AI are definitely underserved.

Yesterday, I met with Anthropic and OpenAI and Google. (Separately, of course.) And while the conversations were largely confidential, I do want to share some aggregated reflections on the day as well as general SF takeaways. ⬇️ 1) Competitive advantage as a solo practitioner really does come from taking action and finding an area with a bit of friction and doubling down. Ex: memory management right now isn’t perfect, but allocating an hour to improving that system gives you a ton of leverage over others 2) SF continues to be the number one place for AI work. I know that’s not surprising. I would put New York at a healthy second place. SF tends to be more about crazy agent experiments for the thrill of capability and discovery and NYC tends to be more about kinda crazy agent experiments to find new ways to make money. Not saying either is better. But I met several people renting two apartments to straddle these worlds. You want the frontier of SF and enterprise insights of NYC. It’s one reason I travel between them so much. 3) All AI labs want to hear more from people. All of them. What are you using it for, what do you like, what do you hate, what do you need. Users have a TON of power on the direction of these tools. Keep testing and tweeting at them!! 4) There is very clearly a third customer cohort that is bubbling and underserved. It’s not developers…it’s not the business professional basic users…it’s builders. Everyone can build now. It’s marketing and sales folks vibe coding. It’s legal folks building complex skills. It’s a finance expert building a side project. This is a really undertapped customer base. They feel the Cursors of the world are too complex and doc summarization tools of the world are too basic. 5) Not sure if it was just sample size, but far fewer people were wearing tech gear compared to when I lived in SF. Everyone was still dressed casually, but I used to see Splunk and Optimizely and Slack and VC gear everywhere. People seem more in stealth swag now. 6) We may soon have our world model moment. 7) Speed of iteration and shipping is faster than I’ve ever seen. We see the nonstop drops from Anthropic. We see that because of scale, providers can get a much faster feedback loop of products or features that aren’t hitting. A lot of 2025 was experimentation, but ever since the OpenClaw moment over the holidays, the releases from all three labs have been more concentrated on…things that sorta look and feel like OpenClaw. 8) Small teams can pull off more than ever before. Small teams are the powerhouses of innovation right now. This means that finding new ways to share knowledge, break silos, and remove duplicate work is going to be even more important. AI agents functioning as actually teammates that support an entire system is key. 9) Build more Skills. Build better Skills. 10) Misinformation on AI tools and leaks spread FAST. I’ve seen so many fake stories on these AI labs. Your company needs to actually TEST these tools on your actual use cases to know which models and tools are best and you need to not make large-scale snap decisions based on a rumor of a rumor of a rumor. We will see more volatility. Plan for it. 11) You can feel the seriousness of this moment. Even during random conversations I had in line at a cafe. Lots of folks worried about job loss and lack of meaning. 12) Mac minis were sold out ;)

@AdamRackis That's one way to put it 😂😂

When your drug dealer complains you’re not doing enough drugs

NVIDIA Nemoclaw's security is worse than I expected. The AI can modify its own config to bypass security controls. I asked it to accept websocket connections from any origin and change its token to something trivial (123). Now any site I visit can give instructions to my bot.

@sterlingcrispin Same. I actually stopped using Claude for writing/auditing code and use Codex for that. Anything code related is Codex's forte, everything else is Claude. I don't have the hard data to back it up, just what I follow based on actual experience of using both tools

Claude 4.6 is a good programmer but writes insanely severe bugs constantly, it won't catch them all in audits, nor will other claudes You need codex 5.4 auditing every commit 4+ times. If you don't believe me, try it. I have an /auditcodex skill for it github.com/sterlingcrispi…

If you are lazy, being the CEO of a successful company is the absolute best job ever. You have to do almost nothing and you get invited to do the coolest shit. Tough job to get though if you’re lazy.

People trying to the world: save the world

True!

Andrew Yang on the coming layoffs.

I've started using Claude. It's great but I can see how someone can spend 20 hours a day on this thing and feel like they accomplished something when they've done nothing.

Just think about this, in the Matrix they called the bad guys “Agents”.

The most dangerous position in 2026 isn't unemployed. It's employed, comfortable, and replaceable. At least the unemployed person knows they need to move.

Backend developers who thought their job was safe

@riajose Tax the rich AND suspend the excise tax on fuel.

TAX THE RICH. TAX THE RICH. TAX THE RICH.

It's getting annoying keeping Claude accountable. I wonder what we can do about this behavior @AnthropicAI @bcherny

@sysadafterdark Same experience but did not cancel OpenAI just yet. Still trying out Codex ....

I just canceled my ChatGPT subscription and switched over to Claude. At least for IT work, Claude has given me much more accurate responses.

The company that sells identity protection just had their data stolen. I’m sure there’s something sarcastic there but I can’t quite put my finger on it…

“Where AI has delivered on their vision.” Number 1: “Productivity” Number 2: “It hasn’t.”

there are some banger quotes in here

@johnennis @GitKraken Cool! Thanks for sharing, trying this out!

Hot tip: When you are running a long loop/run, get Codex/Claude to give you progress reports in the commit statements, so you can just monitor the situation in @GitKraken