When I was becoming a self-taught software engineer it also was hilarious, no doubt about it - and very inefficient. I did enjoy it and did build some stuff, and not all of it was bad.
So, if anything, if the intent is "I can do it all myself and I will fire you now" - I love to see them stumble, if the intent is "I want to get my hands dirty and let's work together" - I will be happy to assist. It's not a pipe dream: it does happen.
Does the journey have value? When you started learning to code to become a software engineer, you probably reasoned that the journey was important.
If you are an exec building an app then the journey is likely to be uninteresting and an impediment to getting to a product. I don't think we'll uncover anything new here that we couldn't reason about before. When execs, or other non-programmers, do get decide to get involved, there is a probability that they will learn something more about software engineering inside their organization. That is the thing that software engineers need to be concerned about because depending on the circumstances, the execs will uncover things which shorten the tenure of SWEs or their management.