I’ve been hearing for quite some time now that I should be using an LLM to plan before the build. This is treating the LLM as the architect, not as a junior being handed small tasks here and there.
I haven’t bought into it, so don’t use it this way, but an army of people online and in the media are pushing the fomo hard and telling people this is how it should be used. If the LLM isn’t doing what we want, it simply means we need to use the LLM even more. That’s the prevailing message from the industry.
Coding, programming and engineering are all a bit different concepts. Coding as in typing in the code might be solved. Engineering? Doubt.
What is definitely not solved is knowing what you want and what user wants and what the end result is supposed to be. To write the code you need the specs and to write the specs you need to know what you want. And that can only be answered by years of therapy.
You can't be mad at people for buying a product from the LLM salespeople and expect the product to comply to the specs they sold you. Be mad at the salespeople scamming customers.
