Project ideas from Hacker News discussions.

If AI writes code, should the session be part of the commit?

📝 Discussion Summary (Click to expand)

1. “Session logs are noisy, but some signal is worth keeping”
Many users argue that raw LLM transcripts are too much to read, yet the decision‑making they contain can help future debugging or training.

“The raw session noise — repeated clarifications, trial‑and‑error prompting, hallucinated APIs — probably isn’t worth preserving… but AI sessions contain one category of signal that almost never makes it into code or commit messages” – claud_ia

2. “Where to store the data matters – git notes vs. external stores”
Git notes are popular because they keep the log out of the main history, but some prefer a dedicated database or a separate folder.

“It runs a commit and then stores a cleaned markdown conversation as a git note on the new commit” – mandel_x
“I keep a directory in the project called ‘prompts’ and an .md file for each topic/feature” – nomilk

3. “Summaries or ADRs are preferable to full transcripts”
The consensus is that a concise, human‑readable distillation (commit message, ADR, plan file) is more useful than the entire chat.

“What actually helps is a good commit message explaining the intent… a one‑paragraph description of the goal and approach is worth more than a 200‑message session log” – yuvrajangads
“The raw session noise… not committing the full transcript, but having the agent synthesize a brief ADR at the close of each session” – claud_ia

4. “AI‑generated code changes the review/reproducibility landscape”
Because LLMs are non‑deterministic, reviewers need more context to judge intent and catch bugs, but many feel the code itself should still be the primary artifact.

“We still need to select for competent/incompetent prompters… if we don’t carefully document AI‑assisted coding sessions, how can we ever hope to improve our use of AI coding tools?” – D‑Machine
“The code is the artifact, a lot of which is incidental… the prompts contain the actual constraints” – claud_ia

5. “Cultural and ethical concerns – privacy, bot content, Show HN noise”
Some participants worry about exposing sensitive data, the flood of bot‑generated projects, and the need for transparency or moderation.

“If the model is set to replace a human – their prompting skill and approach are the only things differentiating them from the rest of the grey mass” – ekjhgkejhgk
“We need a separate ‘Show HN’ for AI posts so that users are not incentivized to spam Show HNs hoping to make it to the front page” – airstrike

These five themes capture the main strands of opinion in the discussion: the trade‑off between noise and useful insight, the mechanics of storage, the preference for distilled artifacts, the impact on review practices, and the broader cultural/ethical context.


🚀 Project Ideas

Generating project ideas…

Gathering the best ideas from the HN discussion…

Read Later