A reset is like a free refill. If your cup (plan) is smaller than your homie’s, every refill gives you less too.
Extra resets are a perk, but somehow make the cheaper plan feel like you’re missing out.
Clever move by OpenAI.
OpenAI's "reset" trick worked insanely well for Codex growth.
Apr 7 → Jul 13: +4M users in ~97 days
Aug 21 → Aug 31: +5M users in just ~10 days
And August is when OpenAI really started leaning hard into the reset trick.
https://t.co/L2k6xbXqu4
Hi @Caltrain, for more than a month, the Wi-Fi has consistently gone down when northbound trains approach Menlo Park. Not sure if you’re aware of the issue, but it would be great if someone could look into it.
Does my manager hate me? Just realized we DM'd for the first time in months. He's the founder and I run marketing...should I be worried?
He hates interruptions and truly means it. We get along great, but tbh I don't hate the lack of DMs...
For the past few months, we've only communicated in a channel with our company's knowledge agent @falconer_ai. It's saved us hours of interruptions and context switching.
"@ falcon is this product claim still true? Check the code and docs."
"@ falcon what did we promise the creative team, and what still needs a decision?"
"@ falcon turn this thread into a creative brief, landing page, and launch plan before we lose the idea."
"@ falcon find the latest doc and update it with what we decided"
When Falconer handles the questions, we go into our 1:1s already on the same page.
@capitaltruist and I get to spend our 1:1s catching up as real people, thinking about the next thing at Falconer, and waiting in the—notoriously long—Golden Goat line.
"Ruined the em dash" will be on my tombstone.
A few years ago I constantly complained to the labs about lack of proper em dash usage. They really pounced on that feedback.
@tobi People are sharing workarounds, but that misses the point. Engineers contributing to the same repo should be free to choose their own tools. I want a healthy coding agent ecosystem, not one company using its lead to push out competitors.
I’m thinking about banning Claude code at Shopify until they change their mind and read AGENTS.md and .agents/skills etc.
Insisting on only reading CLAUDE.md sometimes leads to split brain problems when different team members use different tools. Just unnecessary.
🚢 Marin 535B-A23B started training this week! As usual, the whole process is open.
Voyage plan: pretraining (80%) + midtraining (20%) on 18.75T tokens on 11 x GB200 NVL72 for ~3 months (2.7e24 FLOPs). Post-training will follow.
Before kicking off the run, we trained a 4-rung scaling ladder from 1.6B-A61M (48B tokens) to 27.7B-A1.2B (926B tokens) to debug issues, and to make a forecast of our hero run. This is by far our biggest run, so definitely expecting the unexpected.
In a few years, every big software company will be competing with the major labs.
If you give the labs your data, your context, your business intelligence (whether it's explicit or tacit), you're giving up on your long-term prospects. After true ASI, your half-life is shot.
RSI is coming, and it will eat your business if exposed to it. But it's a paper tiger if it can only feast on synthetic data and purchased slack threads from dead startups.
@harvey, @tryramp, @cursor were years ahead of everyone else with AI. They're showing what the next few years will look like for successful companies by owning your own context and intelligence.
My fear with AI coding agents taking over is that our library ecosystem will stagnate.
We’re unconsciously leaning towards popular frameworks that agents know best and experimenting less with niche tools.
The “new JavaScript framework” meme is dead.
@capitaltruist Spotted the Chinese edition of this book in a bookstore in China and bought it immediately. I promise I’ll find time to actually read it.
Since writing is a hot topic these days, here are two easy sippers for *anyone* in tech—whether beginner or advanced—who wants to immediately uplevel their writing skills.
@FireFlySquid380 I may not have explained it clearly. It wasn’t a cybersecurity task, just ordinary engineering work that GPT flagged as one. I still need to get it done, so I may have to use another model.
OpenAI: Security professionals can apply for access.
Security rookies: Cool, I’ll take the code and data to Kimi K3.
Open-weight models are already close to GPT-5.6, and rookies still have bills to pay. I can’t tell if this reduces risk or just reroutes it.
Give every team and agent a focused home for the knowledge they need.
Spaces reduce noise while keeping shared work connected and searchable.
- Agents only see the context each user can access
- Set permissions once at the space level
- Keep sensitive team knowledge restricted