Failing your local compilation due to linter problems is just stupid.
Sending "temporary" changes into your CI pipeline isn't even stupid, it's borderline malicious.
mmddmm
joined 5 months ago
Hum... The article says it: avoid every one.
Or not, because there is still not enough evidence to conclude it's a problem. It's just "very likely", not "known'.
Hum... Ignore linter advice for code that you temporarily mangled.
It's not like you have to act upon it as soon as a blue line appears under your code.
Their backs point up when they fly, not backwards.
Firefox does that out of the box.
It can only work up to a limiting frequency. It's probably in the visible spectrum or in near ultra-violet (that's how material go). But since it's a video, I won't go check it.
Oh, you will notice the call of the void, don't worry about that.
As scary as the article makes screworms look, that thing doing the calling is way scarier.
Oh, and the worm that died inside its brain once too.
It's one on top of the other, silly AI.
The test is a symptom of whether the text has women as normal characters that do stuff.
But this actual goal is hard to define, and if none of the women do any relevant stuff, they won't have any subject to talk about that doesn't involve a men. That said, the proxy test fails to reflect the actual test all the time.
Ok, you made me look.
Perplexity got the longest, most boring and uplifting article about how it's normal and there's nothing to worry about. It never mentioned that my wife would dislike the idea, so the personalization was off for the day.
Also, it gave no references. What is weird. Like if the text was hardcoded there.
It will generate bad tests, so you will have lots of tests blocking your work, but won't actually test the important properties.
That's an amount of trust in the LLM capacity to not create hidden corner cases and your capacity to review large-scale changes that... I find your complete faith disturbing.