Tap a claim on the ring to put it at the centre.
← Non-monolithic software architectures generally offer better…
17 connected korrents · 16 moments from 26 Jan 2016 to 26 Aug 2026.
Everything filed under software performance
software performance
Everything filed under developer tools
developer tools
Everything filed under LLMs
LLMs
Everything filed under simplicity
simplicity
Everything filed under software quality
software quality
Everything filed under AGI
AGI
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: Non-monolithic software architectures generally offer better scalability and maintainability than monolithic ones.
Non-monolithic software architectures generally offer better scalability and maintainability than monolithic ones.
Last stated 3 years ago
1 Dec 2023
AD
Adam DeHaven — holds since 2023-12-01 — tap for who they are
Same subject: Even at top-100 traffic levels most applications can be served by a simple monolith, and it is cheaper to build than a complex architecture. — tap to centre the map on it
Even at top-100 traffic levels most applications can be served by a simple monolith, and it is cheaper to build than a complex architecture.
Last stated 5 years ago
6 Apr 2022
DL
Dan Luu — holds since 2022-04-06 — tap for who they are
Same subject: Monolithic GitHub projects, rigid organisations and sequential languages all lead to bad software architectures. — tap to centre the map on it
Monolithic GitHub projects, rigid organisations and sequential languages all lead to bad software architectures.
Last stated 11 years ago
26 Jan 2016
JA
Joe Armstrong — holds since 2016-01-26 — 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: There will be many AIs engineered with trade-offs rather than one monolithic AI, because you cannot optimize everything. — tap to centre the map on it
There will be many AIs engineered with trade-offs rather than one monolithic AI, because you cannot optimize everything.
Last stated 4 years ago
28 Apr 2023
KK
Kevin Kelly — holds since 2023-04-28 — tap for who they are
Same subject: Large language models are better at producing locally optimal code than at generating big architectural ideas. — tap to centre the map on it
Large language models are better at producing locally optimal code than at generating big architectural ideas.
Last stated 4 months ago
13 Jul 2026
SS
Salvatore Sanfilippo — holds since 2026-07-13 — tap for who they are
Same subject: Local-first software will not become the dominant architecture, and that is an acceptable outcome. — tap to centre the map on it
Local-first software will not become the dominant architecture, and that is an acceptable outcome.
Last stated 10 months ago
15 Jan 2026
NP
Nikita Prokopov — holds since 2026-01-15 — tap for who they are
Same subject: Scalability is not a property a system has; it is the set of mechanisms it has for coping with a change in load. — tap to centre the map on it
Scalability is not a property a system has; it is the set of mechanisms it has for coping with a change in load.
Last stated 7 months ago
22 Apr 2026
MK
Martin Kleppmann — holds since 2026-04-22 — tap for who they are
Same subject: Micro-services require scalable, resilient scaffolding that conventional SOA frameworks or ESBs do not usually provide. — tap to centre the map on it
Micro-services require scalable, resilient scaffolding that conventional SOA frameworks or ESBs do not usually provide.
Last stated 11 years ago
4 Apr 2016
RC
Rui Carmo — holds since 2016-04-04 — tap for who they are
Same subject: "Is the page loaded?" was never a real question, and web performance only became measurable once it was broken into the distinct moments a user actually notices. — tap to centre the map on it
"Is the page loaded?" was never a real question, and web performance only became measurable once it was broken into the distinct moments a user actually notices.
Last stated 3 months ago
19 Aug 2026
AO
Addy Osmani — holds since 2026-08-19 — tap for who they are
Same subject: "Optimize it later" would be safe advice only if every engineer already knew how to avoid the architectural mistakes that no later optimization can remove. — tap to centre the map on it
"Optimize it later" would be safe advice only if every engineer already knew how to avoid the architectural mistakes that no later optimization can remove.
Last stated 3 months ago
26 Aug 2026
CM
Casey Muratori — holds since 2026-08-26 — tap for who they are
Same subject: A 300-millisecond response budget is not an achievement but an admission: 300 milliseconds is an eternity in computing, and a product pitching it shows how far the bar has fallen. — tap to centre the map on it
A 300-millisecond response budget is not an achievement but an admission: 300 milliseconds is an eternity in computing, and a product pitching it shows how far the bar has fallen.
Last stated 3 months ago
26 Aug 2026
CM
Casey Muratori — holds since 2026-08-26 — tap for who they are
Same subject: A profiler measures time already spent in an operation, not how much time would be saved by optimizing it. — tap to centre the map on it
A profiler measures time already spent in an operation, not how much time would be saved by optimizing it.
Last stated 3 years ago
18 Dec 2023
NE
Nelson Elhage — holds since 2023-12-18 — tap for who they are
Same subject: A tool's speed comes primarily from its design decisions rather than the programming language it is written in. — tap to centre the map on it
A tool's speed comes primarily from its design decisions rather than the programming language it is written in.
Last stated 11 months ago
29 Dec 2025
AP
Aaron Patterson — holds since 2025-12-29 — tap for who they are
Same subject: For GPU performance, flops do not matter so much as the whole memory access pattern does, and torch.compile cannot find every optimization. — tap to centre the map on it
For GPU performance, flops do not matter so much as the whole memory access pattern does, and torch.compile cannot find every optimization.
Last stated 2 years ago
9 Jun 2024
AK
Andrej Karpathy — holds since 2024-06-09 — tap for who they are
Same subject: Compiler mechanisms that force a required optimization to occur, rather than relying on incidental compiler behavior, are a more robust way to write performance-sensitive code. — tap to centre the map on it
Compiler mechanisms that force a required optimization to occur, rather than relying on incidental compiler behavior, are a more robust way to write performance-sensitive code.
Last stated 2 years ago
9 Mar 2025
NE
Nelson Elhage — holds since 2025-03-09 — tap for who they are
Same subject: What clean-code polymorphism really costs you is not the virtual call but the optimizations the compiler can no longer perform once it cannot see what runs. — tap to centre the map on it
What clean-code polymorphism really costs you is not the virtual call but the optimizations the compiler can no longer perform once it cannot see what runs.
Last stated 3 months ago
26 Aug 2026
CM
Casey Muratori — holds since 2026-08-26 — 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 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
At the centre
Non-monolithic software architectures generally offer better scalability and maintainability than monolithic ones.
Last stated 1 Dec 2023 · 3 years ago
Holds Adam DeHaven
Read this korrent →
Similar wording
Even at top-100 traffic levels most applications can be served by a simple monolith, and it is cheaper to build than a complex architecture.
Last stated 6 Apr 2022 · 5 years ago
Holds Dan Luu
Similar wording
Monolithic GitHub projects, rigid organisations and sequential languages all lead to bad software architectures.
Last stated 26 Jan 2016 · 11 years ago
Holds Joe Armstrong
Similar wording
AI coding might shift software towards modular, service-based architectures with clear API boundaries.
Last stated 25 Apr 2025 · 2 years ago
Holds Tom Blomfield
Similar wording
There will be many AIs engineered with trade-offs rather than one monolithic AI, because you cannot optimize everything.
Last stated 28 Apr 2023 · 4 years ago
Holds Kevin Kelly
Similar wording
Large language models are better at producing locally optimal code than at generating big architectural ideas.
Last stated 13 Jul 2026 · 4 months ago
Holds Salvatore Sanfilippo
Similar wording
Local-first software will not become the dominant architecture, and that is an acceptable outcome.
Last stated 15 Jan 2026 · 10 months ago
Holds Nikita Prokopov
Similar wording
Scalability is not a property a system has; it is the set of mechanisms it has for coping with a change in load.
Last stated 22 Apr 2026 · 7 months ago
Holds Martin Kleppmann
Similar wording
Micro-services require scalable, resilient scaffolding that conventional SOA frameworks or ESBs do not usually provide.
Last stated 4 Apr 2016 · 11 years ago
Holds Rui Carmo
Same subject: software performance
"Is the page loaded?" was never a real question, and web performance only became measurable once it was broken into the distinct moments a user actually notices.
Last stated 19 Aug 2026 · 3 months ago
Holds Addy Osmani
Same subject: software performance
"Optimize it later" would be safe advice only if every engineer already knew how to avoid the architectural mistakes that no later optimization can remove.
Last stated 26 Aug 2026 · 3 months ago
Holds Casey Muratori
Same subject: software performance
A 300-millisecond response budget is not an achievement but an admission: 300 milliseconds is an eternity in computing, and a product pitching it shows how far the bar has fallen.
Last stated 26 Aug 2026 · 3 months ago
Holds Casey Muratori
Same subject: developer tools
A profiler measures time already spent in an operation, not how much time would be saved by optimizing it.
Last stated 18 Dec 2023 · 3 years ago
Holds Nelson Elhage
Same subject: developer tools
A tool's speed comes primarily from its design decisions rather than the programming language it is written in.
Last stated 29 Dec 2025 · 11 months ago
Holds Aaron Patterson
Same subject: developer tools
For GPU performance, flops do not matter so much as the whole memory access pattern does, and torch.compile cannot find every optimization.
Last stated 9 Jun 2024 · 2 years ago
Holds Andrej Karpathy
Same subject: compilers
Compiler mechanisms that force a required optimization to occur, rather than relying on incidental compiler behavior, are a more robust way to write performance-sensitive code.
Last stated 9 Mar 2025 · 2 years ago
Holds Nelson Elhage
Same subject: compilers
What clean-code polymorphism really costs you is not the virtual call but the optimizations the compiler can no longer perform once it cannot see what runs.
Last stated 26 Aug 2026 · 3 months ago
Holds Casey Muratori
Same subject: compilers
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