Related posts
Iván Olivares Rojas x.com
Y pensar que alguna vez codeé coffeescript durante un año entero 😅 Linda forma de atar un codebase, la idea era buena en el fondo, pero typescript le ganó la batalla sin duda (y quizá sin pelearla).
TypeScriptcoffeescriptcodebase
The subject this post names, from the same vocabulary the directory files beliefs under, and the words it uses that this site has seen least often elsewhere. Posts are matched on those words alone — nothing here is a summary of this one.
Top people
Showing Profile →
Hiding
Hiding
18 September
14 September
12 September
10 September
6 September
27 August
26 August
-
Their words
everybody on your team who is making architectural decisions, those people must know performance and they must make decisions that will allow the other people downstream of them to use an architecture which can be optimized later. If you don't do that, you're just rolling the dice.
2 August
-
Their words
have I personally shipped some production code and whatnot? Yes. Uh do I think that's really the best use of my time? Not really.
27 July
-
Their words
one example is the model can now rewrite essentially any code base from one language to a different language.
16 July
15 July
From one piece Context engineering with Dex Horthy 4 beliefs, in the piece's order there
-
Their words
I do the research I do the plan I do the implementation I throw the docs out and the next time I need research I just do it from scratch because tokens are cheap and my time is expensive
-
Their words
You'll notice what I said was not use loops to ship the features that users want. We use loops to actually improve the codebase quality and we read all the code because we care about how it's architected and we care not just about the system architecture but what I would call the program design
-
Their words
So I think the the thing I'm most excited is actually like what we call like iterated loops or like slow loops where we basically have a cron job. We have the loop the the the structure of the loop is really easy. It's like run this llinter fix one thing commit and push and then we run that every night in our GitHub actions and we wake up every morning to one PR that makes the codebase a little bit better.
+ 1 more
-
Their words
We tried this. We built a lights off software factory in July of 2025 and by November we had shut it down. I think it takes about three to six months of you shipping all the time with nobody reading the code before you realize like, wow, this is getting way worse and it's easier to start over than it is to fix it.
24 June
-
Their words
Yeah, so I would say over the last 6 months actually we've been cranking a lot of features out a lot of code out. Most of it has been written by AI at this point. And before that really wasn't the case. I was actually a really big AI hater for a long time
-
Their words
An intentional steering layer can not only help but is increasingly needed in software today.
27 May
-
Their words
The thing that I find interesting is that's not novel. This has been the thing we've always been trying to do forever. How do we get a junior engineer to ship code safely without breaking stuff? Right? How do we make patterns in the codebase? How do we make tests? Like it's it's all the old stuff that we've always wanted to do.
18 May
4 May
15 April
-
Their words
But without the handoff, everyone builds. And that makes all the difference.
1 April
-
Their words
we're trying to crack the next frontier which is how we get that level of productivity increase and output building new features on top of a code base that are older,
25 March
From one piece Thoughts on slowing the fuck down 4 beliefs · mariozechner.at
-
Their words
And organizations have super high pain tolerance. But human-made enterprise codebases take years to get there. The organization slowly evolves along with the complexity in a demented kind of synergy and learns how to deal with it. With agents and a team of 2 humans, you can get to that complexity within weeks.
-
Their words
With an orchestrated army of agents, there is no bottleneck, no human pain. These tiny little harmless booboos suddenly compound at a rate that's unsustainable. You have removed yourself from the loop, so you don't even know that all the innocent booboos have formed a monster of a codebase. You only feel the pain when it's too late.
-
Their words
You can give it a Bash tool so it can ripgrep its way through the codebase. You can give it some queryable codebase index, an LSP server, a vector database. In the end it doesn't matter much. The bigger the codebase, the lower the recall. Low recall means that your agent will, in fact, not find all the code it needs to do a good job.
+ 1 more
-
Their words
Worse, you realize that the gazillions of unit, snapshot, and e2e tests you had your clankers write are equally untrustworthy. The only thing that's still a reliable measure of "does this work" is manually testing the product.
19 March
-
Their words
one of the magic tricks about these things is that they they're incredibly consistent. If you've got a code base with a bunch of patterns in, they will follow those patterns almost to a T.
11 March
From one piece From IDEs to AI Agents with Steve Yegge 3 beliefs, in the piece's order there
-
Their words
Where an idea can take root among the agents that's incorrect. It's It's It's a wrong architecture or or wrong data flow or whatever that's that's causing an impedance mismatch for the rest of your code. And what happens is I call it a heresy because they have the tend They have a tendency to to grow and to come back and they're really hard to weed out, okay?
-
Their words
If you're a monolith, you're kind of hosed because I told you the ceiling's going up for what they can do, but it ain't ever going to hit your monolith. They will never fit in the context window and you're never going to be able to never in the next 18 months be able to tell a model go fix my monolith. You have to break it up.
-
Their words
But right now I think it's sitting somewhere between half million and five million lines of code, somewhere in there. Probably more on the half million side right now and with the next drop of an Anthropic model, we're probably going to see it jump up to a few million lines.
10 March
4 March
-
Their words
always make sure that when you start a migration, you finish the migration.
20 December 2025
-
Lovedrcmnd.app
SvelteKitTheir words
elements, JavaScript reigns supreme. SvelteKit's efficiency and reactivity make it my framework of choice, and TypeScript's type annotations bring a welcome layer of confidence to my codebase.
6 September 2025
-
Lovedrcmnd.app
PHPStormTheir words
I started using PHPStorm last year and I love it. I honestly don't know how I managed to live without it. It makes it a breeze to refactor a large codebase or source dive some vendor code.
13 September 2024
-
korrents.com
Mastodon's web client is a heavy React app that breaks without scripting and loads slowly on old hardware.Their words
when you send someone a link to a post, they can't read it without loading the entire Mastodon frontend app into their browser, which will is a monster React codebase that will break if they have scripting disabled and also can take up to 30 seconds on older hardware.
21 May 2024
-
korrents.com
Per-engineer productivity inevitably declines somewhat as an organization and its codebase growTheir words
It is almost inevitable that per-engineer productivity drops to some extent as an organization and codebase grows, even though it's also nearly-impossible to quantify that effect.
17 May 2022
-
Their words
Code has mass. Every additional line of code you don't need is ballast. It weighs your codebase down, making it harder to steer and change direction if you need to.
Professional Programming: The First 10 Yearsthorstenball.com
8 February 2022
1 March 2020
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.