Understanding the problem is easier for me experienced with engaging with solutions to the problem and seeing what form they fail in. LLMs allow me to concretize solutions so that pre-work simply becomes work. This allows me to search through the space of solutions more effectively.
If you thought code writing speed was your problem you have bigger problems
21–30 of 231 posts
Re: If you thought code writing speed was your problem you have bigger problems
#22As human developers, I think we're struggling with "letting go" of the code. The code we write (or agents write) is really just an intermediate representation (IR) of the solution. For instance, GCC will inline functions, unroll loops, and myriad other optimizations that we don't care about. But when we review the ASM that GCC generates (we don't) we are not concerned with the "spaghetti" and the "high coupling" and…
If you truly believe that, why don’t you just transform code directly to assembly? Skip the middleman, and get a ton of performance!
Re: If you thought code writing speed was your problem you have bigger problems
#23If I can offload the typing and building, I can spend more energy understanding the bigger picture
Re: If you thought code writing speed was your problem you have bigger problems
#24[flagged]
[flagged]
Re: If you thought code writing speed was your problem you have bigger problems
#25[flagged]
Re: If you thought code writing speed was your problem you have bigger problems
#26As human developers, I think we're struggling with "letting go" of the code. The code we write (or agents write) is really just an intermediate representation (IR) of the solution. For instance, GCC will inline functions, unroll loops, and myriad other optimizations that we don't care about. But when we review the ASM that GCC generates (we don't) we are not concerned with the "spaghetti" and the "high coupling" and…
If you truly believe that, why don’t you just transform code directly to assembly? Skip the middleman, and get a ton of performance!
Can agents write good assembly code?
Re: If you thought code writing speed was your problem you have bigger problems
#27As human developers, I think we're struggling with "letting go" of the code. The code we write (or agents write) is really just an intermediate representation (IR) of the solution. For instance, GCC will inline functions, unroll loops, and myriad other optimizations that we don't care about. But when we review the ASM that GCC generates (we don't) we are not concerned with the "spaghetti" and the "high coupling" and…
>Source code in a higher-level language is not really different anymore
Source code is a formal language, in a way that natural language isn't.
Re: If you thought code writing speed was your problem you have bigger problems
#28As human developers, I think we're struggling with "letting go" of the code. The code we write (or agents write) is really just an intermediate representation (IR) of the solution. For instance, GCC will inline functions, unroll loops, and myriad other optimizations that we don't care about. But when we review the ASM that GCC generates (we don't) we are not concerned with the "spaghetti" and the "high coupling" and…
If you truly believe that, why don’t you just transform code directly to assembly? Skip the middleman, and get a ton of performance!
you know if I could I would (Android dev)
Re: If you thought code writing speed was your problem you have bigger problems
#29[flagged]
Re: If you thought code writing speed was your problem you have bigger problems
#30> The bottleneck is understanding the problem. No amount of faster typing fixes that. Why not? Why can't faster typing help us understand the problem faster? > When you speed up code output in this environment, you are speeding up the rate at which you build the wrong thing. Why can't we figure out the right thing faster by building the wrong thing faster? Presumably we were gonna build the wrong thing either way in…
>Why not? Why can't faster typing help us understand the problem faster?
do you have a example (even a toy one) where typing faster would help you understand a problem faster?