Tap a claim on the ring to put it at the centre.
← Relying on the semantic meaning of SemVer is not reliable and every…
17 connected korrents · 16 moments from 8 Feb 2017 to 10 Aug 2026.
Everything filed under developer tools
developer tools
Everything filed under design
design
Everything filed under compilers
compilers
Everything filed under open source
open source
Everything filed under software quality
software quality
Everything filed under LLMs
LLMs Same subject Same subject Same subject Same subject Same subject Same subject Same subject Same subject Same subject Same subject Same subject Same subject Same subject Same subject Same subject Same subject Same subject Read this korrent: Relying on the semantic meaning of SemVer is not reliable and every update should be treated as potentially breaking. Relying on the semantic meaning of SemVer is not reliable and every update should be treated as potentially breaking. Last stated 6 years ago
2 Mar 2021
HS
Hynek Schlawack — holds since 2021-03-02 — tap for who they are
Same subject: Major version numbers should not be treated as sacred, and any breaking change deserves a major bump regardless of size. — tap to centre the map on it Major version numbers should not be treated as sacred, and any breaking change deserves a major bump regardless of size. Last stated 4 years ago
23 May 2022
TP
Tom Preston-Werner — holds since 2022-05-23 — tap for who they are
Same subject: Software becomes more robust when the names used inside its code reflect the intention behind it. — tap to centre the map on it Software becomes more robust when the names used inside its code reflect the intention behind it. Last stated 4 months ago
17 Jul 2026
KR
Kenneth Reitz — holds since 2026-07-17 — tap for who they are
Same subject: Users like security in the abstract and experience it as breakage: hardening the project made things slower, harder to update, and broke what people depended on. — tap to centre the map on it Users like security in the abstract and experience it as breakage: hardening the project made things slower, harder to update, and broke what people depended on. Last stated 3 months ago
10 Aug 2026
PS
Peter Steinberger — holds since 2026-08-10 — tap for who they are
Same subject: Veterans of the 1990s free software movement do not understand the world today’s maintainers work in, and should listen before proposing fixes for it. — tap to centre the map on it Veterans of the 1990s free software movement do not understand the world today’s maintainers work in, and should listen before proposing fixes for it. Last stated 3 years ago
1 Apr 2024
TD
Thomas Depierre — holds since 2024-04-01 — tap for who they are
Same subject: The amount of unintentional breakage through updates outweighs the amount of intentional breakage. — tap to centre the map on it The amount of unintentional breakage through updates outweighs the amount of intentional breakage. Last stated 6 years ago
2 Mar 2021
HS
Hynek Schlawack — holds since 2021-03-02 — tap for who they are
Same subject: Use language models for anything, but never to produce slop: whatever you publish carries your name and your credibility. — tap to centre the map on it Use language models for anything, but never to produce slop: whatever you publish carries your name and your credibility. Last stated 2 years ago
8 May 2024
SW
Simon Willison — holds since 2024-05-08 — tap for who they are
Same subject: A compiler that names every place a change breaks turns refactoring into fixing errors until the compiler stops shouting. — tap to centre the map on it A compiler that names every place a change breaks turns refactoring into fixing errors until the compiler stops shouting. Last stated 6 months ago
20 May 2026
AR
Alice Ryhl — holds since 2026-05-20 — tap for who they are
Same subject: On a serverless platform, a runtime upgrade must never break a live application, because developers have no control over when upgrades happen. — tap to centre the map on it On a serverless platform, a runtime upgrade must never break a live application, because developers have no control over when upgrades happen. Last stated 5 years ago
19 Oct 2021
KV
Kenton Varda — holds since 2021-10-19 — tap for who they are
Same subject: A coding AI that integrates only with its own vendor's tools will be very limited compared with one that draws on all the tools you use. — tap to centre the map on it A coding AI that integrates only with its own vendor's tools will be very limited compared with one that draws on all the tools you use. Last stated 3 years ago
16 Mar 2024
QS
Quinn Slack — holds since 2024-03-16 — tap for who they are
Same subject: 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. — tap to centre the map on it 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 6 months ago
13 May 2026
AH
Anders Hejlsberg — holds since 2026-05-13 — tap for who they are
Same subject: A feature-rich native 'view source' option for debugging sites with iPadOS would be beneficial. — tap to centre the map on it A feature-rich native 'view source' option for debugging sites with iPadOS would be beneficial. Last stated a year ago
11 Jul 2025
CO
Christian Oliff — holds since 2025-07-11 — tap for who they are
Same subject: A software engineer who is not using a tool like Cursor is working at half productivity or worse. — tap to centre the map on it A software engineer who is not using a tool like Cursor is working at half productivity or worse. Last stated a year ago
18 Aug 2025
BT
Bret Taylor — holds since 2025-08-18 — tap for who they are
Same subject: AI coding agents work best with the same general-purpose tools built for humans, such as git and file utilities, rather than agent-specific interfaces. — tap to centre the map on it AI coding agents work best with the same general-purpose tools built for humans, such as git and file utilities, rather than agent-specific interfaces. Last stated a year ago
30 Sept 2025
HR
Harper Reed — holds since 2025-09-30 — tap for who they are
Same subject: AI coding assistants remove repetitive work without replacing human judgment. — tap to centre the map on it AI coding assistants remove repetitive work without replacing human judgment. Last stated 9 months ago
17 Feb 2026
EB
Emanuele Bartolesi — holds since 2026-02-17 — tap for who they are
Same subject: Building powerful developer tools such as compilers, interpreters, and query languages requires knowledge of parsing. — tap to centre the map on it Building powerful developer tools such as compilers, interpreters, and query languages requires knowledge of parsing. Last stated 10 years ago
8 Feb 2017
TB
Thorsten Ball — holds since 2017-02-08 — tap for who they are
Same subject: Most macros just transform their arguments, so running them during static analysis is usually safe even though it can't be guaranteed. — tap to centre the map on it Most macros just transform their arguments, so running them during static analysis is usually safe even though it can't be guaranteed. Last stated 3 years ago
31 Dec 2023
PH
Phil Hagelberg — holds since 2023-12-31 — tap for who they are
Same subject: A programming language is not a compiler but an experience: editing, running, debugging and the runtime library all have to fit together as one cycle. — tap to centre the map on it A programming language is not a compiler but an experience: editing, running, debugging and the runtime library all have to fit together as one cycle. Last stated 6 months ago
13 May 2026
AH
Anders Hejlsberg — holds since 2026-05-13 — tap for who they are
At the centre
Relying on the semantic meaning of SemVer is not reliable and every update should be treated as potentially breaking.
Holds Read this korrent →
Major version numbers should not be treated as sacred, and any breaking change deserves a major bump regardless of size.
Holds
Software becomes more robust when the names used inside its code reflect the intention behind it.
Holds
Users like security in the abstract and experience it as breakage: hardening the project made things slower, harder to update, and broke what people depended on.
Holds
Veterans of the 1990s free software movement do not understand the world today’s maintainers work in, and should listen before proposing fixes for it.
Holds
The amount of unintentional breakage through updates outweighs the amount of intentional breakage.
Holds
Use language models for anything, but never to produce slop: whatever you publish carries your name and your credibility.
Holds
A compiler that names every place a change breaks turns refactoring into fixing errors until the compiler stops shouting.
Holds
On a serverless platform, a runtime upgrade must never break a live application, because developers have no control over when upgrades happen.
Holds
A coding AI that integrates only with its own vendor's tools will be very limited compared with one that draws on all the tools you use.
Holds
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.
Holds
A feature-rich native 'view source' option for debugging sites with iPadOS would be beneficial.
Holds
A software engineer who is not using a tool like Cursor is working at half productivity or worse.
Holds
AI coding agents work best with the same general-purpose tools built for humans, such as git and file utilities, rather than agent-specific interfaces.
Holds
AI coding assistants remove repetitive work without replacing human judgment.
Holds
Building powerful developer tools such as compilers, interpreters, and query languages requires knowledge of parsing.
Holds
Most macros just transform their arguments, so running them during static analysis is usually safe even though it can't be guaranteed.
Holds
A programming language is not a compiler but an experience: editing, running, debugging and the runtime library all have to fit together as one cycle.
Holds