> Patching together cherry-picked lines of code from different Red/System files, with zero context...how dishonest. (I give a detailed context and explanation about those lines you have extracted from different sources on a separate page [8], as it is quite long. It also debunks your "no comments" claim as the first line you have picked has 3 comments in the neighbouring lines.)
1. I was looking for exaggerated examples, that's true. It's hardly cherry-picking as lack of parantheses to discern between functions and arguments makes it really hard to read/understand code everywhere
2. How nice of you to provide comments. Which are:
- not even in git, but on pastebin
- Instead of putting that extended description in the code comments, you put them... somewhere.
So far it doesn't look so good for you.
Let's look at the "three neighbouring comments". They have no meaning for anyone looking at the code who's not already familiar with the code. I'm really glad that you said that "we need at least two stops". It makes so much sense.
And, in the end, it still doesn't help the long line where you have no idea what is a function call, and what is just an argument.
Well, unless you scan the entirety of the code because something may be function defined somewhere in the file, some may be variables, some may be something else.
So, so far you've only validated everything I said.
> That gives a 4.83% result...so about 5000 times more than your claim
Wow. You've really, really "put my extravagant claims to the test". Well, you've actually just reinforced my words. A tiny fraction of all bugfixes ever get tests.
> the tests are sometimes provided in a later commit
> we do try to address ... from time to time
I will remain skeptical, as it's really hard to correlate a bug fix and a test that "may be sometimes from time to time" written at a later date.
But it looks like even your ardent supporters don't know about those tests.
Moreover, this approach clearly affects how people approach writing the system. "Oh, there are no tests for the bugfixes, and no comments in the code? when I submit my bugfix, I'll do the same".
> The only honest statement from you I can find is your Twitter account's baseline [7]: "Opinions on things I know nothing about".
Yup. The person accusing me of being arrogant and condescending goes to great lengths to find out who I am and revert to ad hominem attacks.
A real class act you are.
1. I was looking for exaggerated examples, that's true. It's hardly cherry-picking as lack of parantheses to discern between functions and arguments makes it really hard to read/understand code everywhere
2. How nice of you to provide comments. Which are:
- not even in git, but on pastebin
- Instead of putting that extended description in the code comments, you put them... somewhere.
So far it doesn't look so good for you.
Let's look at the "three neighbouring comments". They have no meaning for anyone looking at the code who's not already familiar with the code. I'm really glad that you said that "we need at least two stops". It makes so much sense.
And, in the end, it still doesn't help the long line where you have no idea what is a function call, and what is just an argument.
Well, unless you scan the entirety of the code because something may be function defined somewhere in the file, some may be variables, some may be something else.
So, so far you've only validated everything I said.
> That gives a 4.83% result...so about 5000 times more than your claim
Wow. You've really, really "put my extravagant claims to the test". Well, you've actually just reinforced my words. A tiny fraction of all bugfixes ever get tests.
> the tests are sometimes provided in a later commit
> we do try to address ... from time to time
I will remain skeptical, as it's really hard to correlate a bug fix and a test that "may be sometimes from time to time" written at a later date.
But it looks like even your ardent supporters don't know about those tests.
Moreover, this approach clearly affects how people approach writing the system. "Oh, there are no tests for the bugfixes, and no comments in the code? when I submit my bugfix, I'll do the same".
> The only honest statement from you I can find is your Twitter account's baseline [7]: "Opinions on things I know nothing about".
Yup. The person accusing me of being arrogant and condescending goes to great lengths to find out who I am and revert to ad hominem attacks.
A real class act you are.