[bustling-noose]

I’ve been working with a team of so called ‘junior’ devs and coding is the least of the problems. Design and architecture is by far the most difficult thing for people to understand and get a hang of. A staff engineer won’t replace 2-4 junior devs with LLM. He will focus on the design and architecture and then get 2-4 engineers to execute it with LLMs. The two might sound the same but it’s not. And that’s the difference between understanding software engineering and coding. LLMs make coding easier, not software engineering.

[skydhash]

> A staff engineer won’t replace 2-4 junior devs with LLM. He will focus on the design and architecture and then get 2-4 engineers to execute it with LLMs.

That's already tried (not with LLMs). Especially with CASE tools, UML, and before those, the waterfall process. Building a software is like writing. Only once it's done, you can be really sure you understand the subject. The skill part is to make sure someone else can.

Doing design and architecture is like drafting plans before a war campaign. It helps with planning, but it does not help in winning the battle. There are pocket of complexity that no design can touch, because you would just be writing the software already.