diff options
| author | srdusr <[email protected]> | 2026-03-04 11:18:00 +0200 |
|---|---|---|
| committer | srdusr <[email protected]> | 2026-03-04 11:18:00 +0200 |
| commit | d79f429d801b7cac077c5573070610563f92bbf1 (patch) | |
| tree | 25ce336bb514cd177477a3f680affa8f2aaf0917 /data/packs/technology.json | |
| parent | 5af72f55bb7fb620af740c9da394e093d7f1280a (diff) | |
| download | typerpunk-d79f429d801b7cac077c5573070610563f92bbf1.tar.gz typerpunk-d79f429d801b7cac077c5573070610563f92bbf1.zip | |
Add long passages for people who want a longer sit
Eleven passages of 320 to 600 characters, which is two to four minutes at an
ordinary speed. Five are public domain openings that run long by nature; the
rest were written to run long rather than padded.
The floor in getRandomTextItem stops a test being too short. Nothing stopped
one being long, and the dataset simply had none: before this the longest
passage was 320 characters and there were three of them.
465 passages, longest now 500 characters.
Diffstat (limited to 'data/packs/technology.json')
| -rw-r--r-- | data/packs/technology.json | 10 |
1 files changed, 10 insertions, 0 deletions
diff --git a/data/packs/technology.json b/data/packs/technology.json index 0e1f4fd..c33a06b 100644 --- a/data/packs/technology.json +++ b/data/packs/technology.json @@ -148,5 +148,15 @@ "category": "technology", "content": "Version control does not exist to store code. It exists to answer the question of what changed and why, which is the only question that matters when something has broken and nobody remembers touching it.", "attribution": "Unknown" + }, + { + "category": "technology", + "content": "There are only two hard things in computer science: cache invalidation, naming things, and off-by-one errors. The joke survives because all three are the same problem wearing different clothes. Each is about the gap between a model in someone's head and the thing the model stands for, and each becomes visible only at the boundary where one part of a system hands something to another. Nothing inside a function is ever hard in this way.", + "attribution": "Unknown" + }, + { + "category": "technology", + "content": "The first rule of distributed systems is not to build one. The second is that if you must, assume every message may arrive twice, out of order, or not at all, and design so that none of those is a special case. Systems that treat delivery as reliable do not fail gracefully when it is not; they fail at three in the morning, in a way that takes a week to reproduce, and the fix is almost always the design that was rejected at the start for being too complicated.", + "attribution": "Unknown" } ] |