this post was submitted on 30 Oct 2026
911 points (96.1% liked)
Privacy
11035 readers
920 users here now
A community for Lemmy users interested in privacy
Rules:
- Be civil
- No spam posting
- Keep posts on-topic
- No trolling
founded 3 years ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
Yeah, and I knew a carpenter with 40 years of experience too. He was a shit carpenter, but he always got work because he'd been a carpenter for so long.
I may only have 10 years of experience coding but I can still see how shitty the output is, and even listed an example. No one should be driving a car with the engine strapped to the hood, even if they're good at driving.
If it's some basic program like a simple video game mod that changes a value or two, sure, let the janky ass code do it.
Cryptographic high security stuff though? There's no way in hell that thing isn't going to introduce a security risk.
That said, it is at least useful for finding bugs and security flaws. But that's because an LLM is a statistics machine, and it's therefore better at reading data than it is at creating it.
I always like to say to people with a lot of experience that are still bad: you don't have 40 years of experience, you have 40 times 1 year experience.
Then you should be putting more time into your tools. Nobody uses a blank of wood to hammer something, and then decides 'wow, hammers aren't good tools," you're just using a shit hammer.
And, to be clear, I work in a full-stack environment and regularly generate HTML and CSS without the issue you mentioned... you can't just pull a frontier model without any skills/rules/mcps and expect it to just do the work. You need design docs and thorough rules for your environment. An LLM is a tool, not a developer.
That's totally fair. They can only get ~75% of the way there on crypto stuff rn. Amazing at the other side, though (pen testing)