
Editorialised headline. If you have proof its backed by a corporation feel free to share, otherwise its just making shit up.

Editorialised headline. If you have proof its backed by a corporation feel free to share, otherwise its just making shit up.
I knew this was the real trans agenda :D
What does the black monster symbolise?


Is the app your planning on usingnwith the storage tolerant of storage disconnecting? USB SSDs are fast, but if you bump the cable it may disconnect and cause you issue.


It is over simplified, but there are often implicit requirements that a human would be aware of from the broader context that the LLM may not be.
i.e add is used to increment a health bar, so wrap around doesnât make sense.


int add(int a, int b) {
return a + b;
}
This code is clearly functional, itâll compile and execute.
However, the customer actually needs the code to do a saturating add.
With that knowledge, we can clearly see that the code is not correct. It will not saturate, it will wrap around instead.
Without that knowledge, an LLM will happily write some basic unit tests that wonât cover the saturation edge case, and the bug would live on until its hit in prod.
If youâre lucky, and your function doco is good, the LLM might spot the bug, and notify you.
My personal preference for how to generate tests is to ask the agent to write specific tests. E.g: âwrite a test for add that demonstrates that it saturatesâ.


Timing and tests, name a better migraine duo :D.
We continuously create tests that ensure a process completes in an set amount of time, and every time, we donât give them enough leeway, and the test will fail randomly if the CI runner gets overloaded.


Is reinstalling your Linux from scratch an option? Maybe youâve accidentally broken something?


Testing functionality isnât the same as correctness.


I have experience with AI generated test suites, and while its good for generating coverage, it isnât so good for actually ensuring correctness, which is the actual point.
Iâve watched the robot happily introduce bugs to pass broken tests, and also break tests to match code, and everything in between.
I donât want lots of tests, I want good tests.
Sure, but you are forgetting the convenience.


Is it next to a river?


Machine derived decryption key is basically the same as unencrypted.
Android story is better, but you effectively hold a backdoor. You can push an update that defeats the decryption without any user interaction.
Ideally, decryption should involve the user inputting a pin or password.


Where does the first decryption key come from? Does the user supply a decryption key first, and then supplies a pin? Verifying the pin at the application level means that once its decrypted, the attacker doesnât need the pin at all, they can just read the decrypted data directly.
Iâm fairly sure you are just sending these comments directly to your LLM.


There are a few thousand other developers, any one of them could start working on a replacement if it bothered them enough. Granted, a lot of them will be grey beards who are happy with mailing lists, but still, the overall friction hasnât pushed them far enough over the edge to replace it.


The problem highlighted by this article is the flood of slop. The mailing list is almost irrelevant, because regardless of whatever alternative you use, the flood of slop will still keep overwhelming it.


Git was created because one of those developers actually had a problem. The fact that they havenât tried to replace the mailing list yet suggests they donât actually have a problem with it.


Because they have to nerf him somehow, canât just have worlds sexiest kernel developer getting everyone soaking wet all the time.
12USD for a game with frequent content updates, by an indie dev. Pirating this is just spiteful.