Related posts
Gergely Orosz x.com
Pretty incredible how the skills repo by @mattpocockuk is only 6 months old, and has more stars than the React one. We had to sit down and talk. Timestamps: 00:00 Intro 05:48 How Matt got into tech 10:14 How Matt got into open source 12:58 Joining Vercel 18:39 Total TypeScript 23:21 AI’s impact on technical education 30:32 Building reusable skills for AI coding agents 40:46 The “smart zone” vs the “dumb zone” 45:02 The wayfinder skill 47:52 Why agents excel at software engineering 50:54 “Leading words” 1:01:10 Learning the fundamentals 1:09:17 Local vs. cloud agents 1:12:36 Planning vs. cours…
TypeScriptcoding agentsopen source
The subjects this post names, from the same vocabulary the directory files beliefs under. Posts are matched on those words alone — nothing here is a summary of this one.
Top people
Showing Profile →
Hiding
Hiding
20 September
-
korrents.com
Frontier AI coding agents can now fix complex compiler bugs like LTO issues in about fifteen minutes.Their words
Strap a frontier AI into a good coding harness, show it what's broken, give it all the sources (source.tar), and ~15 minutes later I have a patch.
What's been going on in w64devkit the past yearnullprogram.com
12 September
11 September
8 September
6 September
-
Their words
to make *actually* good software, you have to use it a lot but many people are spending more time in their coding agents/factories than in the apps they're building - so they won't
5 September
4 September
-
Their words
This kind of thing will be exploited. Think Solar Winds–style supply chain attacks.
3 September
-
Recommendstheir ownrcmnd.app
Vercel AI GatewayTheir words
Points all coding agents to AI Gateway, getting you 100% uptime, observability, budgets, and ease of switching.
31 August
25 August
-
Their words
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.
22 August
19 August
-
korrents.com
Coding agents make every plugin interface you ever blew off trivially usable, which is a large productivity win.Their words
I can't say enough how excellent a coding agent is at customizing Chrome with extensions. A huge productivity win. Every plugin interface you've ever blown off is now trivially usable.
14 August
-
Their words
buuuut my roadmap is’nt ten times shorter. and I’m definitely not ten times better at deciding what is worth building. teams haven’t started casually shipping a year of product work every month. you can look around and and it’s hard to say what software has gotten meaningfully better in the last year.
10 August
8 August
-
Their words
I REALLY want to believe that this fixes prompt injection risks for coding agents, but I'm just not there yet
30 July
-
Their words
Um, and to give you an example of a a a use of a coding agent that works extremely well is you can ask today's models to translate software from one computer language to another very effectively because in that case you actually have a incredibly detailed specification.
26 July
-
Their words
we we kind of have coarse level uh recursive self-improvement already. And the fact that every time you use it, it improves the markdown files. Uh every time you use it, it updates its uh long-term memory.
20 July
30 June
27 June
-
Their words
untrusted repos should be treated as hostile by default because they can steer the agent toward reading files, running commands, or sending data through approved tools.
27 May
From one piece Building OpenCode with Dax Raad 2 beliefs, in the piece's order there
-
Their words
We're now doing it in a much heavier way because we find that these like kind of bory enterprisey uh patterns end up being pretty useful because you have a bunch of idiots on your team now. The coding agents are a bunch of idiots and they are going to work 24/7 and they're going to like ship a lot of stuff. So you need way more guardrails than you used to.
-
Their words
And our harness wasn't very good for like the first like five months of open code. But it was good enough. It was good enough that most people couldn't really tell a difference. And once we won enough share, then we went back and like tried to make our harness like good and smart and optimize and all those things. But uh it was inverted from what everybody else was doing. Everybody else was being like you have to build the smartest harness and that's how you win.
28 April
7 April
From one piece Should Designers "Code"? 2 beliefs · lukew.com
-
Their words
There's a question that never goes away in design: should designers code? My answer has always been yes. But for a decade or so, the complexity of front-end development made it impractical for most. Thankfully, AI coding agents have reopened the door.
-
Their words
For years, it was faster to mock up software than to ship it. Designers stayed "ahead" of engineering with prototypes. Now AI coding agents make development so much faster that the loop has flipped.
4 April
3 April
-
Their words
the likelihood of inspiring someone to build a competitor was too high, and the return on sharing was too low to justify the exposure. That threshold has effectively collapsed to zero.
The Increasing Risk of Building in Publicthebootstrappedfounder.com
1 April
-
Their words
it required a different way of thinking and the cognitive load might be a little higher but the output is dramatic and we have seen our best engineer double their output.
20 March
-
korrents.com
What limits you with coding agents is your own skill at stringing them together, not the capability of the models.Their words
I think to a large extent you feel like it's a skill issue. It's not that the capability is not there. It's that you just haven't found a way to string it together of what's available.
19 March
From one piece Simon Willison: Engineering practices that make coding agents work - The Pragmatic Summit 3 beliefs, in the piece's order there
-
Their words
the key thing about TDD is that it means that the agents won't write more than they need to.
-
Their words
I think I see people who are writing code with coding agents and they're not writing any tests at all. That's a terrible idea.
-
Their words
I think that might be what saves us. I think the fact that no, you can't have one engineer and have him do a thousand projects because after three hours of that he's going to literally pass out in a corner.
11 March
-
Their words
So I think we're in a weird limbo for the rest of this year okay where until the UIs arrive that are good enough for everybody who can't read everybody who can't read is going to be a severe disadvantage.
2 March
1 March
13 February
-
Their words
But the quality of these systems isn't just in the code they write. It's also in the code I don't have to write. And maybe more importantly, their actual value is in the code I would never have written, or could never have written, or never would have wanted to write.
When Long-Term Investments Finally Pay Offthebootstrappedfounder.com
12 February
-
Their words
It's the same way as you have to play with a guitar before you can make good music. It's, it's not, oh, I, I touch it once and it just flows off. It, it's a, it's a, a skill that you have to learn like any other skill.
-
korrents.com
Being an excellent programmer is a burden rather than an advantage when learning to work with coding agents.Their words
It’s actually how good they are at programming is almost a burden in their ability to empathize with the system that’s starting from scratch. It’s a totally new paradigm of, like, how to program. You really, really have to empathize.
19 January
-
Their words
But with today's AI coding agents, building software is remarkably easy. So instead of handing over static assets and static guidelines, designers can deliver custom software. Tools that let clients create their own on-brand assets whenever they need them.
8 January
7 January
3 January
31 December 2025
-
Their words
I run in YOLO mode all the time, despite being deeply aware of the risks involved. It hasn’t burned me yet... ... and that’s the problem.
17 October 2025
-
Their words
And I kind of feel like the industry it's it's um it's over it's it's making too big of a jump and it's trying to pretend like this is amazing and it's not. It's slop and I think they're not coming to terms with it and maybe they're trying to fund raise or something like that.
14 October 2025
11 September 2025
15 August 2025
Nothing matches.
What is a korrent?
A korrent is a belief a person has stated in their own words: one sentence stating the claim, backed by a quote and a source, kept at korrents.com.
Under a name here, the quoted block is what they actually said. The korrent beneath it is the claim those words support, in korrents' wording — tap it to see the record, its source, and who else holds it.
Nobody here wrote their own korrents. They are compiled from public statements, and a person can change their mind, which is recorded too.
About the English under a post
Some people here publish in a language other than English. Where they do, this site shows a machine translation beneath the post, in this typeface — the site's own, not theirs.
The post itself is never changed, moved or hidden: what is set in the serif above is exactly what the person published, and it is what to quote them on. A translation can be wrong in ways that matter, especially about tone.
Only the post's own words are translated. A quoted post, a linked article and a belief on korrents.com are left in their original language.