> Really does not sound like that from your description. It sounds like coaching a noob, which is a lot of work in itself.

Even if you do it by yourself, you need to do the same thinking and iterative process by yourself. You just get the code almost instantly and mostly correctly, if you are good at defining the initial specification.

▲

fsloth 6 hours ago | parent [-]

This. You _have_ to write the spec. The result is that instead of spending X units of time on spec and THEN y units of time on coding, you get the whole thing in x units of time AND you have a spec.

The trick is knowning where the particular LLM sucks. I expect in a short amount of time there is no productivity gain but when you start to understand the limitations and strengths - holey moley.

▲

skydhash 5 hours ago | parent | next [-]

> The result is that instead of spending X units of time on spec and THEN y units of time on coding, you get the whole thing in x units of time AND you have a spec.

It's more like x units of time thinking and y units of times coding, whereas I see people spend x/2 thinking, x typing the specs, y correcting the specs, and y giving up and correcting the code.

	▲	fsloth 4 hours ago \| parent [-]
		Sure! That's inefficient. I know just how I work and I've been writing the type of programs I do for quite many years. And I know what would take me normally a week takes me few days at best.

▲

smsm42 3 hours ago | parent | prev [-]

Unless you realize no LLM is good at what you need and you just wasted weeks of time walking in circles.