Comment

Comment by dhanush

> Why an AI specific account?

I'm toying with this idea where my primary account reflects work I did myself and with an LLM agent but I slowed down enough to understand what it did. Where I feel comfortable enough to put my name against that work. Because a lot of AI generated code turns out to be really embarassing and my primary account should portray the best of me.

A secondary account to separate the slop. And by default it can be assumed I didn't really spend much time verifying it all and am going more on "vibes". Eventually work from the AI account may make it into the primary account if its unslop'ed ever.

I haven't yet gone on to create an ai account, but might just do so.

> I imagine you'd like agents to stop signing commits unless asked to, but that would make even actual vibe coding a lot harder to detect.

In the context of $DAY_JOB, I don't think it matters anymore. And 99.99% of the commits is AI assisted / authored, so I find that information both redundant and something that takes away my agency from me. Putting my name on a commit means I take pride in it and that I want to ensure that I did my utmost best to verify it. With an LLM's co-author tag, I find myself slipping easily instead on this metric.

parent dhanush 2 months ago

Discussion

Live from the official Hacker News API

A modern reader for Hacker News · SvelteKit + Skeleton