When you write a library the first step is always designing it. LLMs dont get rid of that step, they get rid of the next step where you implement your design.

▲

xigoi 3 days ago | parent [-]

They also added an additional step where you have to explain your design using vague natural language.

▲

irishcule 2 days ago | parent [-]

Is this really "additional"? do you not do design docs/adrs/rfcs etc and talk about them with your team? do you take any notes or write out your design/plan in some way even for yourself?

Why can't you just pass any of those to an AI?

	▲	whateveracct 2 days ago \| parent \| next [-]
		If I'm writing a library to work with a binary format, there is very little English in my head required, let alone written English. That is a heavily symbolic exercise. I will "read" the spec, but I will not pronounce it in literal audible English in my head (I'm a better reader than that.) I write Haskell tho so maybe I'm biased. I do not have an inner narrative when programming ever.
	▲	xigoi 2 days ago \| parent \| prev [-]
		I’m not part of any team, I work on my projects alone. I rarely write long-form design documents; usually I either just start coding or write very vague notes that only make sense when combined with what’s in my head.