> As a bonus, we look forward to fewer violations (exhibit A, B, C) of our strict no LLM / no AI policy,
Hilarious how the offender on "exhibit A" [1] is the same one from the other post that made the frontpage a couple of days ago [2].
Check out this dude: https://github.com/GhostKellz?tab=repositories
He's got like 50 repos with vibe-coded, non-working Zig and Rust projects. And he clearly manages to confuse people with it:
oh god... he has a humongous AI generated PR for julia too https://github.com/tshort/StaticCompiler.jl/pull/180
My favorite of his https://x.com/joelreymont/status/1990981118783352952
> Claude discovered a bug in the Zig compiler and is in the process of fixing it!
...a few minutes later...
https://github.com/ziglang/zig/pull/25974
I can see a future job interview scenario:
- "What would you say is your biggest professional accomplishment, Joel?"
- "Well, I almost single-highhandedly drove Zig away from Github"
Ah. I remember that guy. Joel. He sold his poker server and bragged around HN long time ago. He is too much of PR stunt guy recently. Unfortunately AI does not lead to people being nice in the end. The way people abuse other people using AI is crazy. Kudos to ocaml owners giving him a proper f-off but polite response.
>MAJOR BREAKTHROUGH ACHIEVED
the bootlicking behavior must must be like crack for wannabes. jfc
>I did not write a single line of code but carefully shepherded AI over the course of several days and kept it on the straight and narrow.
>AI: I need to keep track of variables moving across registers. This is too hard, let’s go shopping… Me: Hey, don’t any no shortcuts!
>My work was just directing, shaping, cajoling and reviewing.
How people can say that without the slightest bit of reflection on whether they're right or just spitting BS
I agree that's a funny coincidence. But, what about the change it wanted to commit? It is at least slightly interesting. It is doubly interesting that changing line 638 neither breaks nor fixes any test.
That one was poorly documented and may have been related to an issue in my code.
I would offer this one instead.
My old rule about the difference between coding and software engineering:
My new rule: