summaryrefslogtreecommitdiff
path: root/lib/rob
diff options
context:
space:
mode:
authorstanley lieber <stanley.lieber@gmail.com>2014-10-06 21:17:26 -0400
committerstanley lieber <stanley.lieber@gmail.com>2014-10-06 21:17:26 -0400
commit081bbcf0a1f25f71bd12e3853ede060b8a82f155 (patch)
treee3c99dcf53d8c6eed21148c9a629279493498a9c /lib/rob
parent5de71b116a9daf647952a84006cc481a6ce259bd (diff)
downloadplan9front-081bbcf0a1f25f71bd12e3853ede060b8a82f155.tar.xz
fortunes: You have an agenda.
Diffstat (limited to 'lib/rob')
-rw-r--r--lib/rob5
1 files changed, 5 insertions, 0 deletions
diff --git a/lib/rob b/lib/rob
index 53be54c7c..85963f98e 100644
--- a/lib/rob
+++ b/lib/rob
@@ -240,3 +240,8 @@ It's not how many features that matter, it's how the features interact.
Just write the code.
Looks like a bug.
And now we have diverged so far from the original question that we can safely ignore it.
+I oversold due to fading memory. But I stand by the fundamental point.
+Although there may be specific examples where generated output is uninteresting, deciding whether to read code based entirely on whether a computer or a human wrote it doesn't seem a good general principle to me.
+Short answer: No.
+None of that is excusable, only true.
+File an issue?