There are also bad suppliers who don't do their leg work. I've "fired" some companies who did great work for me because they couldn't be bothered to send a bill - I know I owe someone some money, but I don't know how much as despite begging they won't tell me how much or where to send it (I only have a phone number) - this bill could get larger, and they can come after me at any time for it...
Please don't be them. If you do good work make sure that you get your bills sent on time.
Fences need to be maintained and are not always where you want them. Cows are big, mostly they are gentle but they can accidentally kill you without trying. Pasture rotation is a big thing but that increases labor costs.
Some ranchers love these because they enable things they should do but won't.
What is the false negative rate and total rates? Without those we are missing too much. If the false negative rate (saying fine but it isn't) then the whole thing is useless. If the total cases are a few hundred (either CASM isn't a problem or those doing it use other platforms cause they know they will be caught on these) I don't care much that some are false positives - odds are it didn't get me.
Sure you can, random sampling should work. Don't just go making things up.
Of course actually carrying out that experiment would be absurd since I don't think anyone expects an appreciable percentage of clearnet material to be CSAM. The working assumption is that the goal is to find a needle in a haystack so GP's objection about needing to know the false negative rate is misguided.
I expect the equivelent of the fbi is investigating this using other sources and so has plenty of data without needing to randomly sample any non-suspect conversation. CASM has been a problem since before computers.
About as bad as I expected. AI can write code I don't feel like - but I still review and understand every line like it is a proven untrustworthy coworker (most are proven trustworthly and get a lesser review). I have found too much outright bugs, race conditions, changing standard required constants and the like.
the problem is people make units too small. A unit is not an isolated class or function. (It can be but usually isn't) a unit is one of those boxes you see on those architecture diagrams.
What I really want is memory order emulation. X86 as strong memory order guarantees, ARM has much weaker guarantees. Which means the multi-threaded queue I'm working on works all the time on development x86 machine even if I forget to put in the correct memory-order schematics, but it might or might not work on ARM (which is what my of my users have). (I am in the habit of running all my stress tests 1000 times before I'm willing to send them out, but that doesn't mean the code is correct, it means it works on x86 and passed my review which might miss something)
For most code it doesn't matter. It matters when you are writing files to be read by something else, or when sending data over a network. So make sure the places where those happen are thin shims that are easy to fix if it doesn't work. (that is done write data from everywhere, put a layer in place for this).
It doesn't really need a shim, if you're parsing incoming data that code should only depend on the endianness of the data, not the endianness of the processor that the code is running on, and in general if you're staying within defined behaviour in C and C++ you're going to need to do this anyway (e.g. https://commandcenter.blogspot.com/2012/04/byte-order-fallac...). If you're concerned about performance optimizers have been able to turn this into the right instructions for decades at this point.
I agree. Dealing with different endianness has never been an issue so long as you're aware of where the boundaries are. A call to htons() or ntohs() (or the 32bit equivalents) was the solution. I would hope all modern languages have similar helper functions/macros.
reply