Hacker News Reader

Comment by password4321 | Hacker News Reader

I recommend making "What are you working on [this weekend/weekly]" official like whoishiring and encouraging pre-Show HN comments there. (https://news.ycombinator.com/item?id=47041973#47043174 "what's the right venue for sharing [LLM-built side projects]")

Also requiring disclosure of the use of AI in repos and especially (or perhaps specifically discouraging its use) when responding with comments to HN feedback.

I'll take this opportunity to strongly encourage sharing prompts (the newest tier of software source code) as the logical progression of OSS adding additional value to Show HN.

View on HN

Combining the two approaches might work. A "pre-moderation queue" for submissions that are are solid enough to pass the "Show" bar, and then the monthly "what are you working on" threads as a more free-form creative outlet.

And yes, disclosing the use of AI should be par for the course.

My issues with the super posts is its really hard to grep for relevant information.

I've tried asking ChatGPT to recommend projects based on my interests, but ChatGPT heavily hallucinated or projected my interests onto irrelevant projects (for example, a project might be about developing a new programming language and chatgpt was like, "you could use this in your soap making hobby!").

The Who's Hiring posts have community sponsored indexers and its easy for me to query job titles relevant to me, but keyword search is not as useful here.

Bruce Schneier had the Friday Squid Blogging posts that he allowed random stuff on. Most of the noise was contained in the Friday threads.

Lobsters had a weekly thread by caius called, "What are you doing this week?" People would post personal projects or experiences in it. On top of interesting tech, that let us pray more specifically for and encourage some in need.

The weekly threads might work here.

My new favorite thing to do is grab the 'What are you working on threads' and have a LLM group them categorically with one line descriptions of each app.

Interesting take on the sharing of prompts. I don’t think this is a bad idea. How would this work though given different prompts occur in different context windows?

Internally, we have a standard that any AI written code simply includes a cut-and-paste of the chat prompt (if that were used), and/or the .md files (if those were used).

I would like to see it as extended comments in each git commit. There have been a few examples of some doing so manually but it needs to be supported by the tooling... with all the half-arsed "standards" like MCP etc. I'm surprised there isn't something already.

Sharing prompts, not sure it works if your project required hundreds of prompts? It’s all in history though (.jsonl) so I’m sure the AI can condense it somehow.

Reply on news.ycombinator.com