32 pointsby handfuloflight9 hours ago3 comments
  • zerof1l2 hours ago
    Next time you write an article with AI, tell it to add a summary at the top. Or, even better, just leave your original thought in one paragraph. I’ve no desire to read kilometers of AI text repeating the same thing over and over. Everybody wins.

    Edit: ok so this whole text concoction is just a product placement for their own service GolemUI

  • Kinrany5 hours ago
    People should really start making a distinction between vibe coding without looking at the actual files, on one hand, and using LLMs as glorified autocomplete.

    Both can be "100% code written by AI" but there's a world of difference between the two.

  • noelwelsh4 hours ago
    Good article. We really need more nuance in the discussion of using LLMs for SE. Not all tasks are the same; we shouldn't expect to use the same process across them!

    In my experience, the more constrained the LLM is, either by existing patterns in the code base or by prior art in general, the better the LLM is. When I've asked it do architectural or design work, it has been much less successful. That's one dimension on which LLM capabilities vary. There are certainly more!

    • shibaprasadb3 hours ago
      Absolutely. When you narrow the solution space by adding more constraints, your probability of success increases. At least, that’s what I’ve noticed.

      For vague, divergent tasks, the overall experience hasn’t been quite as good.