Tap a claim on the ring to put it at the centre.
← The goal of testing should be tests that are easy to understand and maintain, not high coverage of everything.
16 connected korrents · 14 moments from 17 Apr 2012 to 15 Sept 2026.
Everything filed under software quality
software quality
Everything filed under design
design
Everything filed under measuring intelligence
measuring intelligence
Everything filed under documentation
documentation
Everything filed under developer tools
developer tools 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 goal of testing should be tests that are easy to understand and maintain, not high coverage of everything. The goal of testing should be tests that are easy to understand and maintain, not high coverage of everything. Last stated 5 years ago
24 Jul 2021
ML
Marc Littlemore — holds since 2021-07-24 — tap for who they are
Same subject: The main purpose of writing tests is to build confidence in the code, not to find bugs. — tap to centre the map on it The main purpose of writing tests is to build confidence in the code, not to find bugs. Last stated 5 years ago
24 Jul 2021
ML
Marc Littlemore — holds since 2021-07-24 — tap for who they are
Same subject: Making test coverage a target destroys it, because high coverage numbers are easy to reach with worthless tests. — tap to centre the map on it Making test coverage a target destroys it, because high coverage numbers are easy to reach with worthless tests. Last stated 14 years ago
17 Apr 2012
MF
Martin Fowler — holds since 2012-04-17 — tap for who they are
Same subject: Having a goal is the essence of intelligence; a system that only predicts is a behaving system, not an intelligent one. — tap to centre the map on it Having a goal is the essence of intelligence; a system that only predicts is a behaving system, not an intelligent one. Last stated a year ago
26 Sept 2025
RS
Richard Sutton — holds since 2025-09-26 — tap for who they are
Same subject: High code coverage does not guarantee that code is well tested or of high quality. — tap to centre the map on it High code coverage does not guarantee that code is well tested or of high quality. Last stated 7 years ago
4 Feb 2020
MP
Maxence Poutord — holds since 2020-02-04 — tap for who they are
Same subject: Well-written tests can serve as a partial substitute for product documentation. — tap to centre the map on it Well-written tests can serve as a partial substitute for product documentation. Last stated 7 years ago
4 Feb 2020
MP
Maxence Poutord — holds since 2020-02-04 — tap for who they are
Same subject: Conventional testing is not sufficient: crude purpose-built checking tools of a few thousand lines find bugs that testing does not. — tap to centre the map on it Conventional testing is not sufficient: crude purpose-built checking tools of a few thousand lines find bugs that testing does not. Last stated 11 years ago
12 Dec 2015
DL
Dan Luu — holds since 2015-12-12 — tap for who they are
Same subject: Test coverage is a tool for finding untested code and says nothing about how good the tests are. — tap to centre the map on it Test coverage is a tool for finding untested code and says nothing about how good the tests are. Last stated 14 years ago
17 Apr 2012
MF
Martin Fowler — holds since 2012-04-17 — 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: After a decade of Swiss minimalism, design is about to swing back to something far more expressive. — tap to centre the map on it After a decade of Swiss minimalism, design is about to swing back to something far more expressive. Last stated 12 months ago
16 Oct 2025
DF
Dylan Field — holds since 2025-10-16 — tap for who they are
Same subject: Better design does not mean more design: the most obvious designs are often invisible. — tap to centre the map on it Better design does not mean more design: the most obvious designs are often invisible. Last stated 3 years ago
16 Nov 2023
JZ
Julie Zhuo — holds since 2023-11-16 — tap for who they are
Same subject: A good tool raises the floor of what people can build without lowering the ceiling, and almost every tool quietly lowers the ceiling. — tap to centre the map on it 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 a year ago
18 Sept 2025
TL
Tobias Lütke — holds since 2025-09-18 — tap for who they are
Same subject: A new API framework that ignores how existing apps were historically built undermines its own introduction — tap to centre the map on it A new API framework that ignores how existing apps were historically built undermines its own introduction Last stated a month ago
31 Aug 2026
CH
Craig Hockenberry — holds since 2026-08-31 — tap for who they are
Same subject: A programming environment should provide exactly one concurrency model, since offering multiple concurrency implementations at once causes problems. — tap to centre the map on it A programming environment should provide exactly one concurrency model, since offering multiple concurrency implementations at once causes problems. Last stated 3 years ago
4 Jan 2024
RP
Rob Pike — holds since 2024-01-04 — tap for who they are