Hacker News: seagram

New comment by seagram in "Show HN: Openleetcode – local LeetCode runner where tests live in the repo"

seagram — Tue, 18 Aug 2026 18:34:45 +0000

What a great idea for a project. Will try out. Any thoughts on supporting a CLI (or TUI) interface for browsing through the problem sets locally (titles, descriptions, difficulty, etc.)? On that note, open to contributions? And much respect for choosing Haskell.

New comment by seagram in "Show HN: Opening lines of famous literary works"

seagram — Tue, 14 Jul 2026 16:35:08 +0000

"It was inevitable: the scent of bitter almonds always reminded him of the fate of unrequited love." > Love in the Time of Cholera - Gabriel García Márquez

IBM stock drops by 13% after Anthropic publishes a blog post

seagram — Tue, 24 Feb 2026 04:07:25 +0000

Article URL: https://www.businessinsider.com/ibm-stock-price-anthropic-ai-update-cobol-language-software-selloff-2026-2

Comments URL: https://news.ycombinator.com/item?id=47132740

Points: 4

# Comments: 1

Ask HN: Need for AI usage disclosure system?

seagram — Wed, 28 Jan 2026 17:06:05 +0000

With the influx of AI-generated code in open source repos, would there be any need/interest in creating a standard to disclose AI usage?

Something like a markdown document in the project root (like LICENSE or CONTRIBUTING) that explains:

- what level of AI was used (None, Assisted, Fully Generated) - which components used UI (core logic, test, etc.) - what A.I tools were used - who reviewed it (human vs. AI reviewed & tested) - contribution guidelines with AI (may be stepping on the toes of CONTRIBUTION)

I'm sure some repos have this already and each can implement it in their own way. But could a standard that defines a structure to disclose this be helpful?

From the perspective of someone quite inexperienced in open source contribution, not sure if this would be of any help (and to who).

Interested to hear your thoughts on this.

Comments URL: https://news.ycombinator.com/item?id=46798133

Points: 1

# Comments: 0