> If you let it write the code, it does become a management job more than an engineering job.

I disagree. It remains an engineering job. Us software engineers got confused about what the engineering part always was. The engineering part of chemical engineering isn’t cutting piping, welding shit, or rolling metal. The engineering in civil engineering isn’t pouring the concrete, or grading the site.

Yet somehow it’s a prevailing idea that the engineering part of software engineering was typing on keys and naming variables.

▲

archagon 5 hours ago | parent [-]

Writing high-level code was never as mechanical as “cutting piping.” That’s absurd. If that’s how you thought about writing code, you were simply a bad programmer. (Or working on some incredibly boring code.)

▲

Jare 4 hours ago | parent | next [-]

The typing absolutely was mechanical. The thinking what you need to type is what's never been mechanical, and there's plenty of that to do LLM or not.

We took advantage of the typing time to also think, and in many ways typing code served a similar purpose to drafting your thoughts on paper. With an LLM you still think a lot and those thoughts turn into specs, prompts, plans, or whatever workflow you prefer.

▲

_aavaa_ 3 hours ago | parent | prev [-]

Writing the code absolutely was. Every character we had to type was accidental complexity

You are conflating designing the system and instantiating it with code. This is exactly what I’m talking about.

Typing characters absolutely is cutting pipe and pouring concrete. It is not where the engineer was or is.

▲

archagon 3 hours ago | parent [-]

You are conflating system design with high-level programming (with typing, which is trivial and takes almost no time).

	▲	_aavaa_ 3 hours ago \| parent [-]
		What exactly is the distinction you’re making between system design and high-level programming?