Coding is not over. I too once thought as you did. In a previous job, I worked extensively with LabView[1]. Like Reason, you hook up wires to little boxes. Thi

Coding is not over. I too once thought as you did. In a previous job, I worked extensively with LabView[1]. Like Reason, you hook up wires to little boxes. This enables graphical dataflow programming. LabView enables a person with no knowledge of syntax to write a program. It's great! Until your program grows in size. Then, you have a very large and very difficult to understand system of boxes and wires. Debugging becomes increasingly difficult. Users can abstract the wires and boxes away into more boxes, but after more than a few layers of turtles, you start wondering why you're even using a system like this. Later on I discovered that LabView was an instance of a "4GL" and that such things had been around for decades. Although some have been successful in certain niches, to my knowledge no 4GL has ever succeeded as a general purpose programming language. Why is this? It's because textual programming languages are far more general and expressive. Programs written in text are far easier to change, version control, and understand. There is no silver bullet[2]. [1] http://www.ni.com/labview/ http://www.ni.com/labview/ [2] https://en.wikipedia.org/wiki/No_Silver_Bullet https://en.wikipedia.org/wiki/No_Silver_Bullet