I've also been loving the speed Claude has enabled me to move at, and now agree that the coding part of SWE has become LLM-wrangling instead. I now see interacting with an LLM, to build all parts of software, as the new "frontend".

Following this idea, what do people think "backend" work will involve? Building and tweaking models, and the infra around them? Obviously everyone will shift more into architecture and strategy, but in terms of hands-on technical work I'm interested in where people see this going.

▲

supermdguy 7 hours ago | parent | next [-]

I’ve been trying to learn a lot about domain driven design, I think knowledge crunching will be a huge part of the new software development role.

▲

alexpotato 7 hours ago | parent | prev [-]

Was chatting with a friend about this:

"I used to write java code and the compiler turned it into JVM bytecode.

Now I write in English and the LLMs compile it into whatever language I want."

Although as one HN commenter pointed out: English is a pretty bad programming language as it's way more ambiguous than most programming languages.

	▲	sgc 6 hours ago \| parent [-]
		The English language has the ability to be ambiguous, but I bet AI use will change the way we use the English language colloquially, to say more specifically what we mean. I worked as a home inspector for a while. Writing for an LLM is very similar to writing a home inspection report or legal brief (or talking to a group of teenagers). Navigate the minefield with very specific intention.