Pitfalls of premature closure with LLM assisted coding
1–10 of 50 posts
Re: Pitfalls of premature closure with LLM assisted coding
#2I put the examples he gave into Claude 4(Sonnet) purely asking to eval the code, it pointed out every single issue about the code snippets (N+1 Query, race condition, memory leak). The article doesn;t mention which model was used, or how exactly it was used, or in which environment/IDE it was used.
The rest of the advice in there is sound, but without more specifics I don't know how actionable the section "The spectrum of AI-appropriate tasks" really is.
Re: Pitfalls of premature closure with LLM assisted coding
#3I initially thought that layout of the sections was an odd and terrible poem.
Re: Pitfalls of premature closure with LLM assisted coding
#4I put the examples he gave into Claude 4(Sonnet) purely asking to eval the code, it pointed out every single issue about the code snippets (N+1 Query, race condition, memory leak). The article doesn;t mention which model was used, or how exactly it was used, or in which environment/IDE it was used. The rest of the advice in there is sound, but without more specifics I don't know how actionable the section "The spectr…
My experience hasn't changed between models, given the core issue mentioned in the article. Primarily I have used Gemini and Claude 3.x and 4. Some GPT 4.1 here and there.
All via Cursor, some internal tools and Tines Workbench
Re: Pitfalls of premature closure with LLM assisted coding
#5I initially thought that layout of the sections was an odd and terrible poem.
haha! I didn't see it that way originally. Shall take it as a compliment and rework that ToC UI a bit :D.
Re: Pitfalls of premature closure with LLM assisted coding
#6[dead]
Re: Pitfalls of premature closure with LLM assisted coding
#7I think this is correct, and I also think it holds for reviewing human-authored code: it's hard to do the job well without first having your own idea in your head of what the correct solution looks like [even if that idea is itself flawed].
Re: Pitfalls of premature closure with LLM assisted coding
#8I put the examples he gave into Claude 4(Sonnet) purely asking to eval the code, it pointed out every single issue about the code snippets (N+1 Query, race condition, memory leak). The article doesn;t mention which model was used, or how exactly it was used, or in which environment/IDE it was used. The rest of the advice in there is sound, but without more specifics I don't know how actionable the section "The spectr…
It's not about "model quality". Most models can improve code their output when asked, but problem is the lack of introspection by the user.
Basically same problem as copy paste coding, but LLM can (sometimes) know your exact variable names, types so it's easier to forget that you need to understand and check the code.
Re: Pitfalls of premature closure with LLM assisted coding
#9I initially thought that layout of the sections was an odd and terrible poem.
Now that you mention it, me too.
Re: Pitfalls of premature closure with LLM assisted coding
#10I initially thought that layout of the sections was an odd and terrible poem.
Oh wow me too - I kinda like it that way.
But if it’s meant to be a table of contents, it really should be styled like a list, rather than a block quote.