17 connected korrents · 18 moments from 11 Jul 2025 to 3 Nov 2026.
At the centre
Questions whether software that works, performs well, has no bugs, is understood, and can later be modified by an agent should be called slop.
Last stated 2 Oct 2026 · 2 months ago
Holds
Thorsten Ball
Read this korrent →
-
Similar wording
Coding agents may no longer add slop to a codebase, and even if they do, the result is not necessarily unmaintainable.
Last stated 25 Oct 2026 · 4 weeks ago
Holds
Thorsten Ball
-
Similar wording
Agent-written code that runs and passes its tests is not enough: security, maintainability and being able to roll it back still need humans in the loop.
Last stated 7 Jun 2026 · 6 months ago
Holds
Tony Fadell
-
Similar wording
The code today’s models and agents write is very hard to follow: you get better performance without knowing why, and no way to fix it when it breaks.
Last stated 19 Jul 2026 · 4 months ago
Holds
Elizabeth Stone
-
Similar wording
Asked to find a deep bug, coding agents can patch many small issues that feel like progress while steering you away from the real problem; there is still no substitute for expertise.
Last stated 5 Aug 2026 · 4 months ago
Holds
Ben Vinegar
-
Similar wording
A code-review agent works best with a clean context, sharing nothing with the coding agent beforehand.
Last stated 22 Apr 2026 · 7 months ago
Holds
Walden Yan
-
Similar wording
Sharing AI slop is acceptable only if it is never on anyone's critical path and is clearly labelled as slop.
Last stated 23 Oct 2026 · 4 weeks ago
Holds
Hadley Wickham
-
Similar wording
Inconsistent output from an AI product is not necessarily bad; it is how AI behaves.
Last stated 31 Oct 2026 · 3 weeks ago
Holds
Marily Nika
-
Similar wording
The low-quality software that AI makes possible is a mistake to bemoan, because the alternative it replaces was no software at all, not high-quality software.
Last stated 20 Sept 2026 · 2 months ago
Holds
Jamie Brandon
-
Same subject: code generation
A codebase is the most important context an AI agent has, and letting many different models add to it without consistent patterns leads to trouble.
Last stated 3 Nov 2026 · 3 weeks ago
Holds
Derek Briggs
-
Same subject: code generation
A model can now port essentially any codebase from one programming language to another, work that used to take a team over a year.
Last stated 27 Jul 2026 · 4 months ago
Holds
Boris Cherny
-
Same subject: code generation
A strong manual coding background helps developers spot algorithmic weaknesses and flaws in generated code.
Last stated 15 Oct 2026 · a month ago
Holds
Adam Tornhill
-
Same subject: developer tools
A compiler that also serves an IDE has to be lazy and deferred throughout — a different way of building compilers from the one the textbooks teach.
Last stated 13 May 2026 · 6 months ago
Holds
Anders Hejlsberg
-
Same subject: developer tools
A feature-rich native 'view source' option for debugging sites with iPadOS would be beneficial.
Last stated 11 Jul 2025 · a year ago
Holds
Christian Oliff
-
Same subject: developer tools
A good tool raises the floor of what people can build without lowering the ceiling, and almost every tool quietly lowers the ceiling.
Last stated 18 Sept 2025 · a year ago
Holds
Tobias Lütke
-
Same subject: vibe coding
A boring but non-superficial SaaS app that would have done well five years ago might now get no signups because tens of thousands can easily vibe code it.
Last stated 1 Sept 2026 · 3 months ago
Holds
Pieter Levels
-
Same subject: vibe coding
A person at maximum vibe-coding speed has about three productive hours a day, and a company that will not let them stop there is going to break.
Last stated 11 Mar 2026 · 8 months ago
Holds
Steve Yegge
-
Same subject: vibe coding
A screenshot is the fastest, easiest way to build, without having to voice it or type it.
Last stated 30 Jun 2026 · 5 months ago
Holds
Meng To