IMO it's still a problem with LLMs; we still have to build in a way that makes it easier for an LLM to make changes later and arguably it's the same things that made software development easier for humans. IME LLMs tend to not know how to do that for themselves and instead just amplify/copy patterns that already exist.
If an LLM can't pave the way for itself then ultimately shared understanding is required to take advantage of LLMs in the first place.
Would you personally vouch, at your job, for the importance of proper assembly coding standards?
I read a lot of assembly.
Certainly scopes vary, but in my line of work i define memory layout and how this data will be processed myself - thus it's great a compiler might do that, but the result of the computation will not change.
Now in comparison giving an LLM specs ... i a) cannot be sure what the computation will be b) it might be something else on another run.