If you want to complain about LLMs used in software, advocate for a voluntary LLM disclosure published in the docs someplace, so people can make informed decisions.
I don't make the binaries. The compiler does. I just feed in specification called source code.
cargo test --workspace --all-features
The above command runs 2000+ tests. Instead of being toxic, you could have just looked at docs or the code to find them.If there are bugs, etc., that's fair game. Declaring hate for folks because of their approach is not.
On my way to ask all academia and researchers to stop using LLMs for their research. As it's just llm doing the research, right?
the code is open source, why dont you show us what a quality test suite looks like?
I mean, just think about cameras and photography. there's talented photographers, they know how to adjust cameras, they understanding lighting and composition, and yet the camera is what is actually producing the photo... but it's not taboo at all, for anyone to claim credit for taking a photo, no matter their skill level or the quality of the result. It's generally accepted that 'using the tool' is part of the process.
if someone said "i created this photo" it might sound like an odd choice of words, but you wouldn't find the need to 'set them straight' by explaining their camera is actually what created the photo.
you can be a hater all you want, but you're just as annoying as the thousands of vibe-coded projects that are annoying you.