5 ms·

The author of the article mainly talks about agentic programming, code generation, and reasoning. Ans very rightly identifies a big problem with agentic program

The author of the article mainly talks about agentic programming, code generation, and reasoning. Ans very rightly identifies a big problem with agentic programming, in my experience. If developers can't maintain the software without AI, it's doubtful they can steer AI to maintain it either. Maybe this is not true and we can tell AI something like 'reduce the number of lines of code' until the essential software is exposed and pared down to a quantity and modularity that humans can then participate. No doubt, most of the value creation is outside of creating software. But if Nvidia and Anthropic do succeed in making better hardware and better software, then the positive reinforcement loop does seem like it could take off. And coding is a big part of that. Maybe we don't need to understand the code at all? Hard to fathom.

nomel 2mo ago
> Maybe we don't need to understand the code at all? Hard to fathom. Doesn't seem too crazy. This is the life of every customer (and most managers) of a software dev. To fathom it, think of yourself as the unicorn customer that can define projects, specs, and methods with competence, and even make architectural calls, with the AI being the dev. To me, this is the incredibly clear eventuality of our profession, within the next 5-10 years. You writing code will be the same as most devs who try to hand write ASM: you will very very rarely be able to beat the compiler at its own game. And, just as now, there's a very small chance you'll go read what compiler produces.
- FloorEgg 2mo ago
  I'm a decent full stack web developer, who knows almost nothing about kernel architecture or machine code. Before LLMs I could make a functional app, despite not understanding several layers the app ran on top of.
- latentsea 2mo ago
  Those layers are deterministic though...
  - nomel 2mo ago
    Determinism is NOT a requirement, as proven by your existence of software devs. Again, shift the perspective to the people you work for, or to your fellow dev. They get along fine with you, who are also not deterministic. They check your output by setting requirements that you can prove are true in a way that satisfies them. You yourself guarantee correctness by tests, because you learned long ago that you yourself are not to be trusted, and are not capable of writing 100% correct code on first pass, except for the most trivial tasks. Your lack of determinism is built into your workflow, with tools like linters, code analysis, etc, to help deal with it all.
    - hermitShell 2mo ago
      Do you think this necessarily sends us as a society (as a species) towards a future where we eventually stop understanding technology and science itself? Like in Asimov's Foundation or Liu Cixin's 'Taking Care of God'. Maybe we need two tiers of technology. Human in the loop up to the point of AI, and then the AI layer which depends on the human stack.
      - nomel 2mo ago
        As knowledge progresses, less and less people will be able to understand it, as has always been the case with the progression of technology. This is an inevitability since intelligence is something that can only be slightly learned [1]. The passionate, high intelligence, nerds will continue to do what they've always done, being the only, very very small, percentage of society that bothers to understand any of it. Most humans are dumb, from a science perspective. The ability to be successful in science has an intelligence threshold of somewhere around 120 [2], with true innovation requiring much more (as history has shown). Do you see any alternative to 'Taking Care of God', if we continue progressing? But, for coding specifically, coding as an unfortunate consequence of working with computers. We've been increasing abstraction since their inception, so we can do the actual work with them that we're trying to implement with code as a means to implement it. Go ask and older programmer, and he'll say the same sort of "kids these days don't understand computers", because he had to wire up the logic on a breadboard and write machine code in a hex editor, where you use a javascript library without even knowing how to implement an adder!!! [1] https://www.nature.com/articles/mp2014105 https://www.nature.com/articles/mp2014105 [2] https://pmc.ncbi.nlm.nih.gov/articles/PMC6480791/ https://pmc.ncbi.nlm.nih.gov/articles/PMC6480791/

nomel 2mo ago

> Maybe we don't need to understand the code at all? Hard to fathom. Doesn't seem too crazy. This is the life of every customer (and most managers) of a software dev. To fathom it, think of yourself as the unicorn customer that can define projects, specs, and methods with competence, and even make architectural calls, with the AI being the dev. To me, this is the incredibly clear eventuality of our profession, within the next 5-10 years. You writing code will be the same as most devs who try to hand write ASM: you will very very rarely be able to beat the compiler at its own game. And, just as now, there's a very small chance you'll go read what compiler produces.

FloorEgg 2mo ago
I'm a decent full stack web developer, who knows almost nothing about kernel architecture or machine code. Before LLMs I could make a functional app, despite not understanding several layers the app ran on top of.
latentsea 2mo ago
Those layers are deterministic though...
- nomel 2mo ago
  Determinism is NOT a requirement, as proven by your existence of software devs. Again, shift the perspective to the people you work for, or to your fellow dev. They get along fine with you, who are also not deterministic. They check your output by setting requirements that you can prove are true in a way that satisfies them. You yourself guarantee correctness by tests, because you learned long ago that you yourself are not to be trusted, and are not capable of writing 100% correct code on first pass, except for the most trivial tasks. Your lack of determinism is built into your workflow, with tools like linters, code analysis, etc, to help deal with it all.
  - hermitShell 2mo ago
    Do you think this necessarily sends us as a society (as a species) towards a future where we eventually stop understanding technology and science itself? Like in Asimov's Foundation or Liu Cixin's 'Taking Care of God'. Maybe we need two tiers of technology. Human in the loop up to the point of AI, and then the AI layer which depends on the human stack.
    - nomel 2mo ago
      As knowledge progresses, less and less people will be able to understand it, as has always been the case with the progression of technology. This is an inevitability since intelligence is something that can only be slightly learned [1]. The passionate, high intelligence, nerds will continue to do what they've always done, being the only, very very small, percentage of society that bothers to understand any of it. Most humans are dumb, from a science perspective. The ability to be successful in science has an intelligence threshold of somewhere around 120 [2], with true innovation requiring much more (as history has shown). Do you see any alternative to 'Taking Care of God', if we continue progressing? But, for coding specifically, coding as an unfortunate consequence of working with computers. We've been increasing abstraction since their inception, so we can do the actual work with them that we're trying to implement with code as a means to implement it. Go ask and older programmer, and he'll say the same sort of "kids these days don't understand computers", because he had to wire up the logic on a breadboard and write machine code in a hex editor, where you use a javascript library without even knowing how to implement an adder!!! [1] https://www.nature.com/articles/mp2014105 https://www.nature.com/articles/mp2014105 [2] https://pmc.ncbi.nlm.nih.gov/articles/PMC6480791/ https://pmc.ncbi.nlm.nih.gov/articles/PMC6480791/