PatronBernard
Joined 10 years ago
Joined 10 years ago
If a journal receives a paper that is unreadable, it is outright rejected with the comment that it should be made readable, regardless the results in that paper. What is the point of having results if you are unable to convince your audience of those results? You could just as well just sit on them and never communicate them. What is harmful about this process?
It is also totally not what I want for docstrings in code or Powerpoint drafts, where consistency in language is critical.
"excursion" (means: a spike/jump — a value that rises or deviates from baseline, just say spike or outlier)
"legitimate majority-normal baseline" (means: a real majority of normal pixels)
"matched pool of pure-noise ('normal') pixels" (means: the same number of normal pixels, don't bring pools into this)
"ablation" (means: comparing before vs. after — turning a thing on/off to see what changes)
I actually used Claude Code to try and find examples like these but not entirely unexpectedly it had a very hard time detecting these, even though I encounter them like every other sentence. I can imagine this style is great when writing prose, not so much when writing documentation.
Similarly, I tried using Claude Design to make some slides, and the individual slides were fine, but just about every other slide it used different words to denote the same concept, which I would say is the fastest way to lose your audience.
Don't be naive or I might even think you're working for the Chinese :-)
And yes, I am arguing that they should not be released if they cannot be verified within a reasonable amount of time.
Also, how will this impact PhD student who might need this research to get their career started. How will it affect the inflow of junior researchers?
By the way, your tone is very unpleasant. Go outside and touch grass, or have a wank for all I care. You are insufferable.