Tap a claim on the ring to put it at the centre.
← The traditional split between a stable branch and an unstable branch…
17 connected korrents · 18 moments from 22 Feb 2018 to 15 Sept 2026.
Everything filed under design
design
Everything filed under open source
open source
Everything filed under software quality
software quality
Everything filed under Ruby on Rails
Ruby on Rails
Everything filed under vibe coding
vibe coding
Everything filed under documentation
documentation 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: The traditional split between a stable branch and an unstable branch may no longer be the right way to develop software. The traditional split between a stable branch and an unstable branch may no longer be the right way to develop software. Last stated 2 months ago
22 Jul 2026
SS
Salvatore Sanfilippo — holds since 2026-07-22 — tap for who they are
Same subject: Software development does not proceed along a straight, predictable path — tap to centre the map on it Software development does not proceed along a straight, predictable path Last stated a year ago
1 May 2025
JS
John Siracusa — holds since 2025-05-01 — tap for who they are
Same subject: The Rails doctrine's 'progress over stability' is the one point that dated: churn is not progress, and stability turned out to be worth more. — tap to centre the map on it The Rails doctrine's 'progress over stability' is the one point that dated: churn is not progress, and stability turned out to be worth more. Last stated a year ago
12 Jul 2025
DH
David Heinemeier Hansson — no longer holds since 2025-07-12 — tap for who they are
Same subject: Letting non-programmers vibe-code features into a large existing product destroys its architecture, even when every individual change looks defensible. — tap to centre the map on it Letting non-programmers vibe-code features into a large existing product destroys its architecture, even when every individual change looks defensible. Last stated a month ago
26 Aug 2026
DH
David Heinemeier Hansson — holds since 2026-08-26 — tap for who they are
Same subject: Software bugs most often arise at boundaries where reality does not respect the divisions assumed by the source code. — tap to centre the map on it Software bugs most often arise at boundaries where reality does not respect the divisions assumed by the source code. Last stated 3 months ago
17 Jul 2026
KR
Kenneth Reitz — holds since 2026-07-17 — tap for who they are
Same subject: Most of software is not the new stuff; it is old, crappy code somebody has to maintain, and it is full of genuinely hard problems. — tap to centre the map on it Most of software is not the new stuff; it is old, crappy code somebody has to maintain, and it is full of genuinely hard problems. Last stated 2 years ago
22 Mar 2025
TH
ThePrimeagen — holds since 2025-03-22 — tap for who they are
Same subject: Paying a maintainer must not buy a say in the project’s direction; funding and governance have to be kept as separate as possible. — tap to centre the map on it Paying a maintainer must not buy a say in the project’s direction; funding and governance have to be kept as separate as possible. Last stated 5 years ago
17 Mar 2022
FV
Filippo Valsorda — holds since 2022-03-17 — tap for who they are
Same subject: Publishing the source is not the same as developing in the open, and only the second changes how the work actually goes. — tap to centre the map on it Publishing the source is not the same as developing in the open, and only the second changes how the work actually goes. Last stated 5 months ago
13 May 2026
AH
Anders Hejlsberg — holds since 2026-05-13 — tap for who they are
Same subject: Nobody has found keeping specs and code in sync worth the upkeep; the code stays the source of truth. — tap to centre the map on it Nobody has found keeping specs and code in sync worth the upkeep; the code stays the source of truth. Last stated 3 months ago
15 Jul 2026
DH
Dex Horthy — holds since 2026-07-15 — tap for who they are
Same subject: A blank chat box is lazy: it violates the first rule of a good user experience, that it is obvious what you can do. — tap to centre the map on it A blank chat box is lazy: it violates the first rule of a good user experience, that it is obvious what you can do. Last stated a year ago
12 May 2025
JZ
Julie Zhuo — holds since 2025-05-12 — tap for who they are
Same subject: A board game conquers the world when chance and strategy are in balance in it. — tap to centre the map on it A board game conquers the world when chance and strategy are in balance in it. Last stated 10 months ago
12 Dec 2025
IF
Irving Finkel — holds since 2025-12-12 — tap for who they are
Same subject: A browser works better as a single window than as multiple separate windows. — tap to centre the map on it A browser works better as a single window than as multiple separate windows. Last stated 2 weeks ago
15 Sept 2026
CC
Chris Coyier — holds since 2026-09-15 — tap for who they are
Same subject: A good prototype should express a single idea or test a single hypothesis. — tap to centre the map on it A good prototype should express a single idea or test a single hypothesis. Last stated 9 years ago
22 Feb 2018
BF
Bennett Foddy — holds since 2018-02-22 — tap for who they are
Same subject: A small performance gain is not worth the complexity added to achieve it, since complexity's costs compound rather than add. — tap to centre the map on it A small performance gain is not worth the complexity added to achieve it, since complexity's costs compound rather than add. Last stated 3 years ago
6 Dec 2023
RP
Rob Pike — holds since 2023-12-06 — tap for who they are
Same subject: Adding rules and complexity to a system drains it of humanity and fun. — tap to centre the map on it Adding rules and complexity to a system drains it of humanity and fun. Last stated 4 years ago
6 Jun 2022
SC
Steve Coast — holds since 2022-06-06 — tap for who they are
Same subject: A theme system's styles should be low-specificity rather than targeted directly at specific elements. — tap to centre the map on it A theme system's styles should be low-specificity rather than targeted directly at specific elements. Last stated 2 months ago
17 Aug 2026
DR
Dave Rupert — holds since 2026-08-17 — tap for who they are
Same subject: Attribute behavior that depends on CSS layout size rather than an element's natural or declared size is a design trap web authors should avoid relying on. — tap to centre the map on it Attribute behavior that depends on CSS layout size rather than an element's natural or declared size is a design trap web authors should avoid relying on. Last stated 3 weeks ago
14 Sept 2026
TE
Terence Eden — holds since 2026-09-14 — tap for who they are
Same subject: Designers should find what the spec should be and build it in HTML and CSS themselves, not make a product manager's spec look pretty. — tap to centre the map on it Designers should find what the spec should be and build it in HTML and CSS themselves, not make a product manager's spec look pretty. Last stated 6 months ago
8 Apr 2026
DH
David Heinemeier Hansson — holds since 2026-04-08 — tap for who they are