> I'm not sure it's that our job is the most automatable

I don't know. It seems pretty friendly to automation to me.

When was the last time you wrote assembly? When was the last time you had map memory? Think about blitting memory to a screen buffer to draw a square on a screen? Schedule processes and threads?

These are things that I routinely did as a junior engineer writing software a long time ago. Most people at that time did. For the most part, the computer does them all now. People still do them, but only when it really counts and applications are niche.

Think about how large code bases are now and how complicated software systems are. How many layers they have. Complexity on this scale was unthinkable not so long ago.

It's all possible because the computer manages much of the complexity through various forms of automation.

Expect more automation. Maybe LLMs are the vehicle that delivers it, maybe not. But more automation in software is the rule, not the exception.

▲

zdragnar 6 days ago | parent | next [-]

RAD programming held the same promise, as did UML, flow/low/no code platforms.

Inevitably, people remember that the hard part of programming isn't so much the code as it is putting requirements into maintainable code that can respond to future requirements.

LLMs basically only automate the easiest part of the job today. Time will tell if they get better, but my money is on me fixing people's broken LLM generated businesses rather than being replaced by one.

▲

johnecheck 6 days ago | parent [-]

Indeed. Capacity to do the hard parts of software engineering well may well be our best indicator of AGI.

I don't think LLMs alone are going to get there. They might be a key component in a more powerful system, but they might also be a very impressive dead end.

	▲	DrewADesign 6 days ago \| parent [-]
		Sometimes I think we’re like cats that stumbled upon the ability to make mirrors. Many cats react like there’s another cat in the mirror, and I wonder if AGI is just us believing we can make more cats if we make the perfect mirror.

▲

hex4def6 6 days ago | parent | prev | next [-]

This has been my argument as well. We've been climbing the abstraction ladder for years. Assembly -> C -> OOP ->... this just seems like another layer of abstraction. "Programmers" are going to become "architects".

The labor cost of implementing a given feature is going to dramatically drop. Jevons Paradox paradox will hopefully still mean that the labor pool will just be used to create '10x' the output (or whatever the number actually is).

If the cost of a line of code / feature / app becomes basically '0', will we still hit a limit in terms of how much software can be consumed? Or do consumers have an infinite hunger for new software? It feels like the answer has to be 'it's finite'. We have a limited attention span of (say) 8hrs/person * 8 billion.

	▲	QuadmasterXLII 6 days ago \| parent [-]
		the cost of creating a line of code dropped to zero. the ongoing cost of having created a line of code has if anything gone up.

▲

6 days ago | parent | prev | next [-]

[deleted]

▲

tkiolp4 6 days ago | parent | prev [-]

LLMs are just another layer of abstraction on top of countless. It’s not going to be the last layer, though.