I’m not trying to be rude, but it seems like you have a rather narrow definition of what ‘coding’ is. Unless you think computers and the internet are going away, coding isn’t going away either. Writing software is coding.

And your solution… to build a drag and drop interface… with React… is coding, using… open source coding. Even if it becomes usable, there is no way it will cover all cases, and if you want to keep it up to date with new software and hardware, you will have to… code.

Honestly, this doesn’t make much sense.

Also, actual software engineers are paid well because it is a difficult, consuming job that requires lots of knowledge and brain power to do well (better than average). I’ve been spending the last few months building a react-native app and contributing to growing libraries to make other programmers lives easier. I find it a little insulting that you think this is a job for a monkey.

Your assertion about GraphQL getting rid of servers shows your lack of knowledge as well. You need to run your own server to use GraphQL… The GraphQL API is still a middleman, it might just be simpler for you to use, but it definitely won’t cover all cases. Anyways, graphQL is nowhere near the power and speed of SQL, and never will be as useful for querying complex relational data.

In some way, you are correct, that is basically what open source is all about, making it so we have to code less boiler plate and do less work on our own. But the set of problems to solve isn’t finite. It’s not like every time someone makes something easier there is one less thing to worry about. When something becomes easier, something that was virtually impossible before becomes possible.

Coding isn’t going anywhere, but it’s definitely changing.