But what's hard with writing a book is not putting words on a paper. It's organizing thoughts and expressing it in a way that convey what you wish to share.
Same with software.
As a freelancer, I spend a lot of time with my clients speaking with them, watching them work, reading their doc, understanding their culture, doodling on paper.
Because my job is first to extract what they need from them.
They are incapable of doing that. I have yet to meet a client that comes to me with half of the information I need to build their software by themself.
So let's say we figure out a way for people to make software, express the rich and complex though and work flow their task require, yet with a an easy process. Its seems dubious given our past history, but I'll indulge the author.
Now what ?
What would my customer build with that ? They don't even know precisely what they want, let alone what they need.
And then let's say that Jesus descents from the sky and a miracle occur, and their figure it out, and create the product with the unicorn No Code magic tool.
They have no idea how to deal with the changes they are going to need to make. How to adapt to politics. How to make it so that it can evolve. What technical decisions will affect their cost in the future. After all, it's not their job.
The code is not really the hard part of the job.
We keep the code because it fits the problem quite well and make it easy to solve once we have the rest figured out.