Tap a claim on the ring to put it at the centre.
← Calendar-based versioning is much more common than people may think,…
17 connected korrents · 16 moments from 2 Mar 2021 to 28 Sept 2026.
Everything filed under developer tools
developer tools
Everything filed under coding agents
coding agents
Everything filed under compilers
compilers
Everything filed under design
design
Everything filed under Python
Python
Everything filed under LLMs
LLMs
Everything filed under innovation
innovation
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: Calendar-based versioning is much more common than people may think, and top-pinning to the current major version falls on its face with it.
Calendar-based versioning is much more common than people may think, and top-pinning to the current major version falls on its face with it.
Last stated a year ago
6 Jul 2025
HS
Hynek Schlawack — holds since 2025-07-06 — tap for who they are
Same subject: Breaking changes should be released frequently in small batches rather than saved up for one big yearly major version. — tap to centre the map on it
Breaking changes should be released frequently in small batches rather than saved up for one big yearly major version.
Last stated 5 years ago
23 May 2022
TP
Tom Preston-Werner — holds since 2022-05-23 — 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 5 years ago
23 May 2022
TP
Tom Preston-Werner — holds since 2022-05-23 — tap for who they are
Same subject: Relying on the semantic meaning of SemVer is not reliable and every update should be treated as potentially breaking. — tap to centre the map on it
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: Letting customers pin old runtime versions would undo part of the promise of serverless: that developers should not have to worry about updating their stack. — tap to centre the map on it
Letting customers pin old runtime versions would undo part of the promise of serverless: that developers should not have to worry about updating their stack.
Last stated 5 years ago
19 Oct 2021
KV
Kenton Varda — holds since 2021-10-19 — tap for who they are
Same subject: Every security update will lead to a spike in n-day exploits in the wild because models are good at reverse engineering. — tap to centre the map on it
Every security update will lead to a spike in n-day exploits in the wild because models are good at reverse engineering.
Last stated 2 months ago
28 Sept 2026
DM
Diogo Mónica — holds since 2026-09-28 — tap for who they are
Same subject: Dropping legacy protocols and old library support is the nature of things: a project has to keep up with reality. — tap to centre the map on it
Dropping legacy protocols and old library support is the nature of things: a project has to keep up with reality.
Last stated 2 months ago
25 Sept 2026
DS
Daniel Stenberg — holds since 2026-09-25 — tap for who they are
Same subject: Release management is human group sense-making, and it does not scale to the volume of change AI now produces. — tap to centre the map on it
Release management is human group sense-making, and it does not scale to the volume of change AI now produces.
Last stated 8 months ago
22 Mar 2026
NF
Nicole Forsgren — holds since 2026-03-22 — tap for who they are
Same subject: AI coding might shift software towards modular, service-based architectures with clear API boundaries. — tap to centre the map on it
AI coding might shift software towards modular, service-based architectures with clear API boundaries.
Last stated 2 years ago
25 Apr 2025
TB
Tom Blomfield — holds since 2025-04-25 — tap for who they are
Same subject: A language can keep changing without a Python-2-to-3 break, as long as code written under the old and the new rules can be mixed freely in one program. — tap to centre the map on it
A language can keep changing without a Python-2-to-3 break, as long as code written under the old and the new rules can be mixed freely in one program.
Last stated 6 months ago
20 May 2026
AR
Alice Ryhl — holds since 2026-05-20 — tap for who they are
Same subject: Certain programming languages are better suited for agents because strong types and annotations help models understand intent. — tap to centre the map on it
Certain programming languages are better suited for agents because strong types and annotations help models understand intent.
Last stated 9 months ago
8 Mar 2026
RC
Rui Carmo — holds since 2026-03-08 — tap for who they are
Same subject: In the age of uv it is time to reconsider ad hoc Python project layouts. — tap to centre the map on it
In the age of uv it is time to reconsider ad hoc Python project layouts.
Last stated 2 years ago
24 Feb 2025
HS
Hynek Schlawack — holds since 2025-02-24 — tap for who they are
Same subject: "I don't know" becomes a kind of superpower when you can work with Claude Code to figure things out. — tap to centre the map on it
"I don't know" becomes a kind of superpower when you can work with Claude Code to figure things out.
Last stated 8 months ago
19 Mar 2026
KP
Kris Puckett — holds since 2026-03-19 — tap for who they are
Same subject: A code-review agent works best with a clean context, sharing nothing with the coding agent beforehand. — tap to centre the map on it
A code-review agent works best with a clean context, sharing nothing with the coding agent beforehand.
Last stated 7 months ago
22 Apr 2026
WY
Walden Yan — holds since 2026-04-22 — tap for who they are
Same subject: A coding agent does not learn from its mistakes the way a person does -- it repeats the same error indefinitely unless a human notices and writes it down. — tap to centre the map on it
A coding agent does not learn from its mistakes the way a person does -- it repeats the same error indefinitely unless a human notices and writes it down.
Last stated 8 months ago
25 Mar 2026
MZ
Mario Zechner — holds since 2026-03-25 — 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: 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
Same subject: A speed difference between languages that share the LLVM backend measures the benchmark author, not the languages. — tap to centre the map on it
A speed difference between languages that share the LLVM backend measures the benchmark author, not the languages.
Last stated 2 years ago
22 Mar 2025
TH
ThePrimeagen — holds since 2025-03-22 — tap for who they are
same subject or similar wording a cloud: claims about one subject, named for it bar: when it was last stated, on a scale from 2015 to today — full is today a face: someone who holds the claim — tap it for who they are