←back to thread

Development speed is not a bottleneck

(pawelbrodzinski.substack.com)
191 points flail | 1 comments | | HN request time: 0s | source
Show context
marginalia_nu ◴[] No.45139149[source]
I would reconcile the seeming paradox that AI-assisted coding produces more code faster, yet doesn't seem to produce products or features much faster by considering that AI code generation and in particular CoPilot-style code suggestions means the programmer is constantly invalidating and re-building their mental model of the code, which is not only slow but exhausting (and a tired programmer makes more errors in judgement).

It's basically the wetware equivalent of page thrashing.

My experience is that I write better code faster by turning off the AI assistants and trying to configure the IDE to as best possible produce deterministic and fast suggestions, that way they become a rapid shorthand. This makes for a fast way of writing code that doesn't lead to mental model thrashing, since the model can be updated incrementally as I go.

The exception is using LLMs to straight up generate a prototype that can be refined. That also works pretty well, and largely avoids the expensive exchanges of information back and forth between human and machine.

replies(2): >>45139921 #>>45140673 #
1. bckr ◴[] No.45139921[source]
I’m moving this way as well after about 6 months of generating 95% of my code with Cursor/Claude.

My new paradigm is something like:

- write a few paragraphs about what is needed

- have the bot take in the context and produce a prototype solution outside of the main application

- have the bot describe main integration challenges

- do that integration myself — although I’m still somewhat lazy about this and keep trying to have the bot do it after the above steps; it seems to only have maybe 50% success rate

- obviously test thoroughly