Remix.run Logo
The age of token efficiency, the age of libraries(golemui.com)
26 points by handfuloflight 5 hours ago | 3 comments
noelwelsh 43 minutes ago | parent | next [-]

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!

shibaprasadb 9 minutes ago | parent [-]

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.

Kinrany 2 hours ago | parent | prev [-]

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.