Agreed. The constraints of software engineering are mostly idiomatic. I used to use my "Scribe" mind to crawl through library dependencies for days to solve some artificial sub-problem.

No software engineer is good enough to time-efficiently write the whole stack from machine code up - it will always be an arbitrary and idiomatic set of problems and this is what LLMs are so good at parsing.

Using "Scribe" cycles to define the right problem and carefully review code outputs seems like the way.