As a guy taught how to design languages, I find this interesting.
The critical thing you really do is define the problem you want to deal with and then select the methods, tools, resources, and supplies to do that task in the time frame, within the costs, and deal with the inevitable failures
you will encounter.
That is not coding.
It is called engineering.
A skill most all “High Tech” coders don’t have a clue about.
You need software engineers and architects to design the flow and hld and to some level lld, but for the grunt worm it may be better to use coders as well, there are more of them and cheaper. And invest in great qa, preferably pessimists who believe there is something wrong with the code.
Long retired Engineer….
Rust, Golang, Hasura, Postgres, GraphQL API, REST, GQL, CRUD, S3, etc etc
But of course..... easy as pie.
I can barely do html/css to create a simple webpage.
Good, Fast, Cheap
You can have 2 of the 3, but not all.