4 ms·
> This is how we've devolved to doing more of what's failed spectacularly. This was the red flag line to me. I haven't heard anyone ever propose "let's do mor
by PaulDavisThe1st 6y ago
> This is how we've devolved to doing more of what's failed spectacularly.
This was the red flag line to me.
I haven't heard anyone ever propose "let's do more of what's failed". What I do hear is people saying "we got that wrong, and here's the minor tweak we need to fix it".
You wrote some code:
for (int i = 0; i < len; ++i)
copy (src[i], dst[i]);
It fails to copy the final element of src to dst. It"fails spectacularly" every time. Eventually you realize that you compute "len" as an inclusive count, not exclusive. You suggest:
for (int i = 0; i <= len; ++i)
copy (src[i], dst[i]);
as a way to make it work.
This isn't "let's do more of what's failed spectacularly". This is "let's make what we're trying actually work". Sure, someone could come along and suggest that we use Algol or brainfuck to solve the issue instead, and that's not a priori insane. But a clear minded reading of the situation - we've got a lot of stuff right, but made some mistakes - would favor trying to fix what we've done wrong, not stop doing what we're trying to do.
The cynicism of this analysis mostly ruined the rest of the piece for me.
- deleted 6y ago[deleted]