Most active commenters
  • simonw(3)

←back to thread

165 points gdudeman | 14 comments | | HN request time: 0.884s | source | bottom
Show context
amelius ◴[] No.44481831[source]
> I've been building software for the Mac since 2008

Ok, so they knew where Claude went wrong and could correct for it.

replies(2): >>44481884 #>>44481892 #
1. simonw ◴[] No.44481884[source]
Right: tools like Claude Code amplify existing skills and expertise, they don't replace it.
replies(2): >>44482030 #>>44483160 #
2. risyachka ◴[] No.44482030[source]
The main issue here is you can’t acquire expertise by using llm to code for you.

So unless you have 15+ yoe better add more reps. You can always switch to llm code assist in a blink, there is no barrier to entry at all.

replies(3): >>44482065 #>>44482329 #>>44482373 #
3. willsmith72 ◴[] No.44482065[source]
> The main issue here is you can’t acquire expertise by using llm to code for you.

Agreed, but I wish I had it as a teacher while learning. The amount of help my interns need from me has reduced by at least 50%, and what remains is the non-trivial stuff which is completely worth my time to coach and mentor them

4. nojito ◴[] No.44482329[source]
>The main issue here is you can’t acquire expertise by using llm to code for you.

You learn far far faster from reading code and writing tests than you do just writing code alone.

I've long suspected for years that the bottleneck to software development is in code generation not keeping up with idea generation.

replies(1): >>44482589 #
5. AnotherGoodName ◴[] No.44482373[source]
I tend to learn via code examples. 20+ years of experience and the llms have taught me about some features of libraries i was using but overlooked.

I think they add to expertise honestly.

replies(1): >>44482441 #
6. freedomben ◴[] No.44482441{3}[source]
I wonder how common this is. Personally, looking at code examples can be helpful, but the vast majority of my learning comes from doing, failing, trying a different approach, succeeding, rinsing and repeating.

I also haven't had much luck with getting llms to generate useful code. I'm sure part of that is the stack I am using is much less popular (elixir) than many others, but I have tried everything even the new phoenix.new , and it is only about an 80 to 90% solution, but that remaining percentage is full of bugs or terrible design patterns that will absolutely bite in the future. In nearly everything I've tried to do, it introduces bugs and bug hunting those down is worse to me than if I just did the work manually in the first place. I have spent hours trying to coach the AI through a particular task, only to have the end solution need to be thrown away and started from scratch.

Speaking personally, My skills are atrophying the more I use the AI tools. It still feels like a worthwhile trade-off in many situations, but a trade-off it is

replies(1): >>44483037 #
7. risyachka ◴[] No.44482589{3}[source]
You learn by trying to solve the problem by yourself.

This is not about syntax but about learning how to create solutions.

When you read solution you merely memorise existing ones. You don’t learn how to come up with your own.

replies(1): >>44483844 #
8. cosmic_cheese ◴[] No.44483037{4}[source]
I also have not had much luck with LLMs when it comes to anything with substantial complexity.

Where I’ve found them best is for generating highly focused examples of specific APIs or concepts. They’re much better at that, though hallucinations still show up from time to time.

9. kiitos ◴[] No.44483160[source]
In my experience they very consistently diminish existing skills/expertise...
replies(1): >>44483567 #
10. simonw ◴[] No.44483567[source]
Hate to say it, but that means you're holding them wrong.

If they diminish your skills, you're letting them do that. Learn to apply these tools in a way that helps you learn more things and do better work.

replies(2): >>44489806 #>>44524605 #
11. nojito ◴[] No.44483844{4}[source]
>When you read solution you merely memorise existing ones. You don’t learn how to come up with your own.

You can't solve programming problems without reading code.

Period.

The more code you read the better you get at solving problems because your internal knowledgebase grows.

12. Leave_OAI_Alone ◴[] No.44489806{3}[source]
The ability to spin up a single page tool for converting timestamps or counting tokens or analyzing a few hardcoded weasel words is handy: nobody disputes that. But that is not the work most of us do.

In the real world, away from those whose salary depends on marketing these agentic tools, an LLM is a context shredder. It provides plausible code snippets that are globally incoherent and don't fit style. CONVENTIONS and RULES files are a kludge, a sloppy hack.

These tools flatten the deep, interconnected knowledge required to work on complex systems into a series of shallow, transactional loops that pretend to satisfy the user.

The skill being diminished is not the ability to write a single-page utility or single-purpose script. It is the ability to build and maintain a mental model of a complex machine. The ability to churn out a hundred disparate toy tools is not evidence of a superior learning method, it is evidence of a tool that excels at tasks with no deep interconnected context.

replies(1): >>44490811 #
13. simonw ◴[] No.44490811{4}[source]
Building the stuff on https://tools.simonwillison.net only represents about 10% of the coding work I do with LLMs.

I wrote about my process for non-vibe-coded projects here: https://simonwillison.net/2025/Mar/11/using-llms-for-code/

> The skill being diminished is not the ability to write a single-page utility or single-purpose script. It is the ability to build and maintain a mental model of a complex machine.

That's the thing that LLMs help me with 90% of the time. It's also why I don't think non-programmers armed with LLMs are a threat to my career.

14. kiitos ◴[] No.44524605{3}[source]
Please, please tell me how I can hold an LLM correctly. My requirements are: it doesn't tell me anything that it's hallucinated, or which is factually incorrect. That's it. That's the only requirement.