[phito]

> If I do ask an LLM another question about something small it will offer solutions but doesn’t offer the solution I think makes sense in the architectures I’ve written.

This is my experience as well, and I've been using Claude Code a lot.

Extremely impressive tools, but they're like fast food. They will solve your immediate problems quickly and cheaply, but you're going to have issues on the long term if that's all you use.

[njovin]

Have you tried drilling into the reasoning when this happens? This is why I usually leave it in "Plan Mode" and when it proposes a solution that seems unusual or unexpected, I point out why I think it is and ask it to justify it's position.

Sometimes I get the "you're right!" response, but often it will also explain why it made the decision it did, and it's rational enough that I accept the new approach.

It's still very much like a junior dev in this way - pretty good at 'just make it work', pretty good at monkey-see-monkey-do, and occasionally surprises you with something novel (to you).

[aselimov3]

> Sometimes I get the "you're right!" response, but often it will also explain why it made the decision it did, and it's rational enough that I accept the new approach.

I think this is kind of what I’m worried about. Referencing Karpathy, an LLM can basically convince any one of anything. Doing this enough times and your opinions just become the LLM opinion. Same with problem solving approaches. I see this for myself so I reserve time to formulate my own solutions. Maybe my solutions are worse but at least I’m training the muscle that may lead to me outperforming the LLM in specific spaces

[Folcon]

> LLM can basically convince any one of anything This and revision to the mean I think are real problems

I've found myself on more than one occasion just stepping away and needing to really sit down and think and to not ask an LLM until I have a clear idea of what I want to do

The one thing that bothers me is that one process I really used to run is thinking in code, slowly sketching out a solution until it had the properties I wanted it to have

I find myself not really engaging with this at present and it really bothers me, I've been trying to figure out how to get back into doing it again because I think the most differentiated and interesting ideas and thinking I had were usually shaped by going through that process

However so far I've found working with LLM's just doesn't jive with that thought process and several months into using them I'm still figuring out how to go back to doing that

[scruple]

How much time do I want to spend on this vs. just writing the old-fashioned way?

[hnthrow0287345]

Fast food might be the right approach if it's a business that prefers speed to maintainability, and they might move towards that with LLMs. I wish more developers would go with it instead of fight it. It's not like it's a personal failure you can't convince the business to slow down and prefer quality.

The quality of the craft can live on in open source and personal projects.

[phito]

I agree, just like some people decide that they're OK with eating junk food every day, knowing the long term risk. They are free to take it.

[grebc]

Lol sure thing Sam!

[hnthrow0287345]

More like developers who give quality away for free then are left wondering why businesses who make millions still end up squeezing the life out of them.