31–40 of 54 posts
Earlier quoted context omitted.
Self-fulfilling prophecy?
I mean attempting to demonstrate something broken, only for it to work properly.
Definitely a thing!
What's the word for this: * My code doesn't work and I can't find the bug even after over an hour * I add a few lines of . Now it works! * Now, just for comparison, I remove all the code I just added (or, at least I think I reverted back to previous state). But now it still works. ???
Though it depends on the cause - as others in this comment chain said, if it's just that the file isn't actually being updated between tests, but adding a new line forces an update/recompile/etc., I'm not sure what you'd call it.
What's the word for this: * My code doesn't work and I can't find the bug even after over an hour * I add a few lines of . Now it works! * Now, just for comparison, I remove all the code I just added (or, at least I think I reverted back to previous state). But now it still works. ???
Choose an editor with autosave to fix this one.
What's the word for this: * My code doesn't work and I can't find the bug even after over an hour * I add a few lines of . Now it works! * Now, just for comparison, I remove all the code I just added (or, at least I think I reverted back to previous state). But now it still works. ???
What's the word for this: * My code doesn't work and I can't find the bug even after over an hour * I add a few lines of . Now it works! * Now, just for comparison, I remove all the code I just added (or, at least I think I reverted back to previous state). But now it still works. ???
* The program works flawlessly
* Somebody finds a bug on the code that is executed in a test
* The relevant test now fails consistently
Both are probably because you changed something on the environment when you looked at the code.
What's the word for this: * My code doesn't work and I can't find the bug even after over an hour * I add a few lines of . Now it works! * Now, just for comparison, I remove all the code I just added (or, at least I think I reverted back to previous state). But now it still works. ???
O Lambda the Ultimate, bless we who are in this demo...
That our core be functional,
and our functions be pure.
That our data be immutable,
so we may know the value of values.
That our systems be composable,
so they may scale with grace.
That their States only mutate
in pleasantly surprising ways.
That the networks and servers stay up.
Well, at least through this demo.
For otherwise, nothing lives, nothing evolves.
In the name of the \alpha and the \beta and the \eta...
\(\lambda x.x x\) \(\lambda x.x x\) ; eternally
(edit: formatting)
What's the word for this: * My code doesn't work and I can't find the bug even after over an hour * I add a few lines of . Now it works! * Now, just for comparison, I remove all the code I just added (or, at least I think I reverted back to previous state). But now it still works. ???
There's the alternative: * The program works flawlessly * Somebody finds a bug on the code that is executed in a test * The relevant test now fails consistently Both are probably because you changed something on the environment when you looked at the code.