At my company, we are focusing more on business automations than software factories. While we develop our own software, we are not a software company but a provider of services. We are benefitting far more from having agents triage alerts, Jira and GitLab issues, review code and deployment requests and answer questions for staff by researching across our internal systems than we would from churning out more code.
5
0
3
471
I enabled step_model_switching in Codex so that I can disable ultrafast mid-turn. The problem with the default is that if I leave it on during tests and peer reviews, it burns tokens at the ultrafast rate checking status unnecessarily. There is no command completion callback and they limit sleep to 60s max. A watch mechanism like Claude provides would be nice.
2
0
1
270
Kevin retweeted
I'm beginning to think that most software engineers will end up not reading the code and maybe not even verifying the work they are doing since it's much easier to just instruct the agents to do that.
I also think that each company will have a couple of very experienced staff engineers that will build agentic systems (custom AGENTS.md, custom skills, various plugins, etc) so the code that the rest of the developers generate will match the code quality standards of the company.
These people will probably read thousands of lines of code every day, understand the code patterns, and probably perform large-scale refactors. Their big challenge will be to act based on data, not on vibes.
This will maybe be controversial, but there's a good chance that the overall output will be higher quality code than two-three years ago as long as the people building the agentic systems know what they are doing.
I also think that each company will have a couple of very experienced staff engineers that will build agentic systems (custom AGENTS.md, custom skills, various plugins, etc) so the code that the rest of the developers generate will match the code quality standards of the company.
These people will probably read thousands of lines of code every day, understand the code patterns, and probably perform large-scale refactors. Their big challenge will be to act based on data, not on vibes.
This will maybe be controversial, but there's a good chance that the overall output will be higher quality code than two-three years ago as long as the people building the agentic systems know what they are doing.
49
9
255
27,042
Introducing tsrs: a Rust port of the TypeScript compiler 🦀
We are not forking TypeScript!
◆ In close collaborating with the TypeScript team
◆ Up to 8x faster than TS 7.0 & ~70% less memory
◆ Runs in WASM, so it works in your browser & on Workers
◆ Soon part of the Oxc toolchain
npx tsrs
blog.cloudflare.com/typescript-rus…
1
0
4
298
Your agent should be able to control the app in any way you can, with proper thread-scoped access controls, of course. Heck, mine can even control client-side settings on individual devices like toggling voice functions. 😀
WTF.
You can schedule tasks in T3code just by asking...????
Why isn't this feature blasted absolutely everywhere?
This would have saved me so much fucking time.
1
0
5
954
A lot of the work I'm doing involves big, well scoped tasks where Claude will take a full day to implement. I am blown away by its attention to detail and how it will remember small things I drop into the chat, or decisions it needs to inform me about after completion. This may be due to memory features in the harness or training around keeping a log (which you can do yourself), but it just works well out of the box. With 1M context and it's use of subagents, it almost never needs to compact. I am no fan of Anthropic but they are providing the better developer product right now.
0
0
2
327
Kevin retweeted
Codex 🤝 Tailscale
Codex Cloud can now securely connect to resources on your tailnet with Tailscale.
Useful tools should be easy to build with, combine, and turn into something even more useful.
See how it works →
buff.ly/yFcldrC
Codex Cloud can now securely connect to resources on your tailnet with Tailscale.
Useful tools should be easy to build with, combine, and turn into something even more useful.
See how it works →
buff.ly/yFcldrC
156
441
5,193
1,234,599
Here we go.
x.com/kcosr/status/2…
x.com/kcosr/status/2…
@claudeebum: you'll get half the usage you used to, and they hop to release more and more efficient (cheaper) models with more capability, so you can still get the same thing done...
They want to converge pricing of API and subscription value, so in the future you might as well pay API pricing.
translation^2: subsidies are coming to an end.
0
0
1
599























