Hacker News Reader

Why does it matter. It's pretty normal to do a bunch of dev locally and then at some point create a public gh repo and then push

View on HN

you can do that with full git history, the first commit is "upload files" or something like that, which I assume is via the UI because that is def not dev speak

Not necessarily. Plenty of devs (me included) clean up or reinit git history before a first release or going public. I understand it’s now read as an AI slop signal, but that’s no reason to dismiss their work.

its not the only reason it is sus, I imagine you too use several dignals, likely evolving in the age of ai

You could, but why is it important?

Are you asking why transparency in the git history and how the code was created is important?

How do you git bisect when a bug was introduced in the mega-commit paradigm? This generally beneficial most for the primary developer.

Separately, the presence of mega commits is a red flag in the age of ai and slop. It's a warning sign for too much eyes-free coding. The agents are not good enough for this. If you are not staying in the loop and managing changes, then I have serious concerns about the security and reliability of the software.

Reply on news.ycombinator.com