Claude Code (desktop/mobile) should really allow you to set a project (new) as the default screen you open to
every open of the mobile app for me is spent on navigating to the main project I’m working in
cc @ClaudeDevs @claudeai
1
1
128
Mamdani’s NYC is probably where I’d consider moving if I ever was to make the jump across the pond at some point
1
68
man, we’re cooking some great stuff up at yaay right now
exciting for December, the experience is gonna look completely different
1
4
248
is it an American thing to take pride in paying hidden fees?
it seems almost cultural? tipping, menu lists price without taxes, paying healthcare as insurance instead of a tax, etc etc
42
there's something that irks me about the Jensen/nvidia thing
i think it's in the massive difference in consequences for Jensen v.s. what the insane things, open corruption, etc that the Trump-o-sphere has done
1
25
right, of all the people in the US doing shit, we’re gonna go with that now are we?
Nvidia’s co-founder came to believe that he was too important for the normal rules to apply to him. This culture of impunity must end. It has damaged one of America’s great corporate successes and undermined its national security economist.com/leaders/2026/1…
33
it is fucking crazy how many systems are getting hacked these days
“we got hacked” emails are almost a daily occurrence now 💀
1
55
in B2C, friction during onboarding is often necessary in order to deliver value
a completed onboarding to only churn right after is worth nothing
this is often jarring when demo’ing your app, but you’re not optimizing for demos, you’re optimizing for real users
Ollie was one of the most interesting vertical AI agents out there for a while.
From their data, the number of external apps a user connects directly correlates with W4 retention:
0 -> 3.5%
1 -> 18%
2 -> 40%
3 -> 52%
That's exactly why we're trying to build for believers first at Quest. People who are willing to connect multiple sources.
We'll probably lose a lot of users initially because of that friction. But that's fine.
It will allow us to listen to the right users, keep iterating on making the product better (because, yes, we know we have a lot to do), and ultimately I'm confident that more and more people will see the value in opening up more to their agents.
Meanwhile, we'll stay heads down building for the right users.
21
the last 10-20% of a feature still takes 80-90% of the time
building is definitely not a bottleneck for us anymore, but crafting a good experience is not a solved problem with AI
Christian Kjær retweeted
Americans are tired of being told their needs are unrealistic by politicians who have been bought by the wealthiest people in the country.
i just don’t understand why people keep thinking Penix is a viable QB for the Falcons
he’s too stationary making him predictable, too injury-prone making him take less chances, and just hasn’t proven it at all yet
1
42
gross misuse of power by Meta locking out other agents, the EU will probably be the only ones that will crack down on this
1
104
monorepos are 100% without a doubt a benefit for agents
type checking across your entire stack, the knowledge of how everything interacts, and atomic changes across the entire stack and infra
When I first told @MParakhin that we were planning to move to a monorepo he said wisely:
Moving to a Monorepo is an idea that every engineer absolutely hates, and that once its there, no engineer would ever want to work at a company that doesn't use one. We will definitely do it.
1
34
REST is for spaghetti code, GraphQL is for structure
enforcing structure on agents is good
therefore GraphQL is good
24
got my boy Claude to go ham on the rust graphql library we were using (async-graphql) because the compile times were insane
not only did it reduce compile times of cold builds by ~40% and rebuilds by ~80% but also reduced allocations by ~60%
zero runtime regressions 👌
2
3
138
shared the learnings with upstream, most of the gains didn’t require any breaking changes at all
github.com/async-graphql/asy…
10







