Hacker News

New stories

Live mirror
30 storiesupdated just nowView source snapshot
  1. Show HN: Four-Leaf MCP, open-source job search and interview prep(github.com/fourleafai ↗)
    discuss
  2. ReadWhile. read while you work(apps.microsoft.com ↗)
    1comments
  3. Maybe Meta Is Right About AI, or at Least Jeremy Stern Is(philippdubach.com ↗)
    discuss
  4. Anthropic at $2T isn't far-fetched(ft.com ↗)
    discuss
  5. Physics in the Age of LLMs(ozamram.substack.com ↗)
    discuss
  6. Hermes Agent now supports Claude Pro/Max subscriptions(nousresearch.com ↗)
    discuss
  7. You Probably Don't Need Another Infrastructure Project(medium.com/majid.fekri ↗)
    discuss
  8. Measurements for understanding the pace of AI development inside frontier labs(anthropic.com ↗)
    discuss
  9. Saudi CEER just launched 2 EVs(ceermotors.com ↗)
    discuss
  10. Show HN: Artwork List – map of artworks near you(artworklist.com ↗)
    discuss
  11. Show HN: Combinators in Array Languages(softwarewrighter.com ↗)
    discuss
  12. Writing Without Spaces with Jev(levmiseri.com ↗)
    discuss
  13. I gave an autonomous AI company $0 and $200 of debt(autonomouscompany.substack.com ↗)
    discuss
  14. AI-Induced Dehumanization(wiley.com ↗)
    discuss
  15. State attorneys general agree to settle Paramount-Warner Bros merger lawsuit(cnn.com ↗)
    discuss
  16. Halo: Post-train LLMs 3x faster than TRL and Megatron(twitter.com/whitecircle ↗)
    1comments
  17. A (necessarily) brief history of the reminder of mathematics(cofault.com ↗)
    discuss
  18. Grok 4.7(twitter.com/spacexai ↗)
    discuss
  19. Show HN: Gitstats – compare commits and lines with your friends(gitstats.org ↗)
    discuss
  20. David Pogue: '125 Tests of the New AI Siri'(daringfireball.net ↗)
    discuss
  21. The Long Dream of the Googlebook(theverge.com ↗)
    1comments
  22. The Next AI Infrastructure Challenge Is Before the First Token(radicaldatascience.wpcomstaging.com ↗)
    discuss
  23. Show HN: I made a Pomodoro timer that speeds up time(arsh.zip ↗)
    discuss
  24. Show HN: Viaduct – C4 models that coding agents can read and update(quietgridlabs.com ↗)
    discuss
  25. OpenAI Urges U.S. Government to Create Global AI-Safety Standards(wsj.com ↗)
    discuss
  26. Apple M6 SoC Analysis's 2 nm chip crushes AMD, Intel and Qualcomm(notebookcheck.net ↗)
    discuss
  27. Show HN: Snagr – abandoned checkout emails for Polar(snagr.sh ↗)
    discuss
  28. Rings around a tiny body have changed over the past decade(arstechnica.com ↗)
    discuss
  29. X's Updates to Terms of Service(privacy.x.com ↗)
    discuss
  30. Show HN: 8 months extending my terminal to handle all my work with all agents(github.com/albertwujj ↗)
    discuss

Ask HN: Formatting Guidelines for LLM Comments

2 pointsby 48m ago
0 comments
Does any prompt or system exist which addresses this issue?

I tend to write my code comments in a very idiosyncratic way, and LLMs either don't understand that (nor do I expect them to), or it isn't much worth explaining. I'm fine with normal LLM comments, but publishing to production means I often have to do a lot of manual clean up with comments when committing code, and that's tedious.

It would even be fine if LLMs all commented the same, but they don't. I actually like the way some LLMs comment, but others are horrendous. The inconsistency is what makes this a mess, and simply saying "no comments whatsoever" (though it works) is hardly an alternative. What I want is a clean, consistent format with strict guidelines on what, and importantly what not, to comment, that works for all LLMs.

The idea here being that I can go on my merry way coding with agents, and that going forward they'll always output perfectly understandable code which I'll never have to check again.

Is there any progress here?

A quiet thread, for now.Start the conversation on HN ↗