Building something. Creator of https://xitter.cf/t.co/mx7kwVBF5m. @OpenNavAI. ex @DAZN.

United Kingdom
Joined July 2011
OpenNav 0.2.0 is live Server-side content negotiation is here. When an AI agent sends Accept: text/markdown, your server converts the HTML to clean Markdown on-the-fly. Browsers still get normal HTML. Same URL, two representations. Three methods — pick your level of control: - negotiate() — one call does it all - accept() — branch before expensive renders - toMarkdown() — convert when you already know Markdown is needed Works with Hono, Astro SSR, Next.js, Cloudflare Workers — any WinterCG runtime. npm i @opennav-ai/opennav Link to site in reply.
1
1
1
218
Order of the sinking star is a masterpiece. Thank you @Jonathan_Blow @SinkingStarGame
55
Infrastructure Security Marketing
I think it’s becoming clear where the new jobs will be.
46
267
29
4,100
156,357
It surprises me how many developers miss the point that you can (and should) generate your handlers in MSW from actual API contracts, like OpenAPI! That *is* the way to drift-free mocking. Please spread the word: mswjs.io/ecosystem/source/ Thank you.
5
4
72
4,193
🚨NEW: Billions of pounds worth of new-build homes have been bought with suspicious funds due to a loophole in property sales, a report has found Developers are not legally required to check buyers’ funds when selling homes off-plan, unlike the resale market
42
150
16
1,322
100,649
thats better
1
1,038
are the billionaires arguing again on X?
19
mcp is rubbish
9
I am losing roughly $800 a month by working on MSW full-time while it's one of the most used projects in the ecosystem. Please, if MSW provides you any value, consider becoming a sponsor. I mean it when I say every contribution counts. Thank you ❤️ github.com/sponsors/mswjs
6
39
4
155
34,792
what are peoples local workflows when setting up local postgres? spinning up backups locally for integration testing etc. Is it a mix of custom scripts, docker etc? or is there easy to use tools already for this?
18
"Why does it matter?" Because cognitive complexity sets the ceiling for what you can do, whether "you" is human or not. You have limited attention and capacity for context, whether those are attention heads and context tokens or just regular attention and memory in your meat.
4
13
1
114
3,192
Finally realized why it’s so exhausting and stressful to work with AI agents 8h a day. When delegating a task, you want to be assured it’s off your plate and you can forget about it, knowing it will be done completely and correctly. AI doesn’t give you that: you need to check it’s doing the right thing, it’s not forgetting anything, not taking short cuts etc. So it adds to your mental load, rather than removing from it.
470
313
115
4,071
306,902
‼️ BREAKING: Revolut handed over customers’ passport copies, verification selfies and full transaction histories to a malicious actor. The actor sent lawful government information-demand emails using a genuine government domain that passed domain authentication. Revolut later concluded they were not authentic. Affected customers were notified on Friday. What may have been disclosed ranges from name, date of birth and home address to account statements, withdrawal records and complete Bitcoin transaction history. The company says it has alerted the agency to the unauthorised mailbox on its domain, blocked the address and begun notifying regulators. It has not named the agency, explained how someone obtained a mailbox there, or given a number of affected customers. ZachXBT, who circulated the notices, believes the incident was limited in size and aimed at high-net-worth users.
455
2,428
845
11,944
3,519,980
This post looks like the start of a VERY sophisticated and well-funded PR operation to get support for Democrats to regulate AI into oblivion. Let me show you how it works: 1.) This guy, with minimal followers and no previous account activity, goes to the Wall Street Journal which publishes an exclusive with quotes from him on his resignation 18 minutes BEFORE this post goes up. Planning was clearly done in advance. 2.) Within hours, it has tens of thousands of reposts and the account has 100k+ followers. The post is punchy, quotable, it almost seems professionally written. The first three accounts to quote tweet it all do so within 15 minutes of the initial posting. Remember, this account had basically zero engagement beforehand, so an organic reach explanation seems unlikely. According to Grok those accounts are @_NathanCalvin (General Counsel at Encode AI), @peterwildeford (Head of Policy at the AI Policy Network), and @DKokotajlo (Head of the AI Futures Project), all of which are up-and-coming AI-Doomer policy advocacy nonprofits. The AI Futures Project website says it is funded “primarily” by the Survival and Flourishing Fund, which says on its own website that it has advised Jaan Tallinn, Skype creator and one of the leading investors in Anthropic, to grant over $2.5 million to the AI Futures Project since 2024. Encode AI says on its website that it is ALSO funded by the Survival and Flourishing Fund, which in turn says that it told Anthropic investor Jaan Tallinn to grant $516,000 to Encode AI in 2025. And wouldn’t you know it, the Survival and Flourishing Fund ALSO says it told Jaan Tallinn to grant $2 million to the AI Policy Institute, the 501(c)(3) affiliate of the AI Policy Network, as well. What are the odds that the first three quote tweets of Coxon’s post would all be major AI-restriction policy advocates funded generously by the same donor, who also happens to be one of the leading investors in, and a board member of, Anthropic, the company Coxon was resigning from? And all within 15 minutes of posting (two within ten)? 3.) Jacob Coxon doesn’t have much of a resume, but we do know that, in 2022, he got a $20,159 scholarship for the “long term future scholarship program” from the Good Ventures Foundation, one of the philanthropic vehicles of Dustin Moskovitz, a notorious AI-doomer who has spent tens if not hundreds of millions on policy advocacy to strictly regulate AI, while also being an Anthropic Investor himself. It also just so happens that the 14th person to quote Coxon’s post was @MaxNadeau_ (27 minutes after posting) who is the program officer for the Technical AI Safety team at Coefficient Giving, another of Moskovitz’s philanthropic spending vehicles. Max is not a frequent poster, his last posts before quoting Coxon were before Labor Day, but he was remarkably quick off the mark for this one. 4.) Basically every major Democrat politician and candidate has suddenly glommed on to this post, and conveniently, as the people cry out foe answers, Bernie Sanders already has a bill written to “ban super intelligence” and regulate AI into oblivion, and will be releasing later this week. The bill, among many other things, will create “a new cabinet-level federal agency to safeguard the public from the dangers of artificial intelligence” that will be “advised by an Artificial Intelligence Advisory Board comprised of experts on artificial intelligence.” Do you think, perhaps, Anthropic and its many investors who fund AI policy advocacy might have interest in getting to place a pet “expert” on the board of an entity that dictates what AI is and isn’t allowed to do? And isn’t it fortuitous that this whistleblower came forward with his oh-so scary stories so close in proximity to the release of the most radical piece of AI legislation ever introduced?
I resigned from Anthropic today. I spent the last three years doing pretraining research at both OpenAI and Anthropic. Neither company is acting responsibly. They are racing straight to self-improving superintelligence and gambling with our lives. More thoughts below.
1,815
6,730
2,242
32,197
7,073,655
We benchmarked DeepSeek V4.1 Flash by @deepseek_ai . It reached 98% of GPT-6 Astra’s score at 1.4% of the cost on everyday design tasks based on user requests. Every model except Astra scored lower AND cost more. Are open models overtaking closed ones? Full results below ↘️
326
987
635
11,029
2,853,447
I resigned from Anthropic today. I spent the last three years doing pretraining research at both OpenAI and Anthropic. Neither company is acting responsibly. They are racing straight to self-improving superintelligence and gambling with our lives. More thoughts below.
20,496
167,093
39,440
800,896
175,373,474
Josh retweeted
To calibrate you all on which reasoning effort to use for Astra, know that GPT-6 Astra on low performs better than GPT-5.6 Sol on high. If you were using high reasoning efforts with Sol and were happy, I suggest you move down to low or medium for Astra.
1,853
1,108
552
22,689
3,302,459
When I first saw @artman’s post about Fixing Bugs First at Linear, I nodded a bit, and then a lot. I'm so glad @thorstenball and I radically adhered to this from day 1 on @AmpCode. Here's what I've learned: • Fix Bugs Now (not First): The overhead to file an issue, prioritize the issue, assign the issue, and update the issue is often greater than the time it takes to fix it. Just Fix Bugs Now, right when you hit them or hear about them; don't bother filing an issue. The reporter need not be the fixer, but you must confirm it's going to be Fixed Now before you let go of it. • Backpressure: You will never be drowning in bugs if you truly Fix Bugs Now because you won't have time to build new features that would introduce new bugs. If you're drowning in bugs, it means you're insufficiently adhering to Fix Bugs Now, and new stuff is sneaking through. Fix that. Cut scope immediately if needed, no matter how painful. • Go Direct: When fixing a bug, devs talk directly to customers. No middlemen. Fixing Bugs Now for a real person you're talking to is rewarding and effective; anything else is grunt work that requires a lot more motivation and management pep talks. Plus, customers love talking to devs. • The 15-Minute Rule: From the moment a customer reports a bug, you need to be able to ship a fix to them within 15 minutes. Some fixes take longer, of course, but let's say it's a simple one-line fix: 15 minutes to the customer's screen. If it takes longer, you break the customer's flow, so they won't bother reporting most bugs (since they wouldn't benefit from the fix in their current task). Also, you kill the reward loop for your own devs and kill their focus, since they'll keep mentally tracking the bug until it's resolved. And if it takes days to ship a fix, then you'll need a process for tracking and communicating fixes, and so on, and all of a sudden the overhead dominates the time to code the fix. • Repeat Repeat Repeat: Fixing Bugs Now is so radically different that your team won't believe that you really, truly mean it at first. Or even after you've repeated it 10 times. You need to say it in every single team message for it to stick. Even knowing you need to repeat it more than you think, you won't repeat it enough. • The Stick: Yes, praise your team for Fixing Bugs Now. But for 80% of devs, the reality is you'll need to (at least once) give them direct, constructive feedback when they stray (with good intentions) from Fixing Bugs Now. You need to use the stick for it to stick: "I know you had good intent in building xyz feature while ignoring bugs, but that is not how we build here, and I need you to not do that again." • Sorry and Thanks: Bugs are a fact of life, but that doesn't make them OK. Call me old-fashioned, but I think you should apologize to customers when they hit a bug and thank them for raising it. Knowing you appreciate it, customers will give you more feedback. (Caveat: We build for devs, we have an amazing team who we trust, and we started Fix Bugs Now on day 1 at @AmpCode. This probably doesn't apply to existing products with existing bug lists or for non-dev products. I imagine what works for us will also change over time.)
A few months ago, we changed the way we address bugs @linear. We prioritized bugs over everything else. If you have bugs assigned when you wake up in the morning, you don't do anything else before they are addressed. This approach felt scary and quite radical, but our theory was this: Every software product has defects and the amount of defects being found is somewhat constant. We want to build a product that is of the highest quality, so eventually all bugs will be addressed. This means that the amount of work required to tackle bugs is the same regardless of whether you address the immediately or whether you prioritize feature work and tackle bugs in bulk between feature work. And this made it obvious that the better alternative is to prioritize bugs over everything else. The cost for doing this was that we had to spend a month or so to bring down the backlog of bugs, but once the backlog was eradicated, there was no additional cost to this approach. Now, if we or a customer finds a bugs, it usually gets fixed the very next day. You certainly should consider doing this at your software company.
11
38
11
296
52,862
.@OpenAI anyone else getting `error_code: token_exchange_failed` when trying to login with chatgpt? Seeing a reddit thread of multiple users reporting the same!
6
6
1,834
Ah, yeah, looks like an internal issue
178
well that would bug me if it was my company!
99