“Ballerina” Could Become the Programming Language of Integratio
hackernoon.com
hackernoon.com
You don't. You need a new paradigm, which is modular flow-based programming. There is nothing to be gained from learning yet another set of syntax rules when computers already do that job better than humans do. It's like trying to design a better running shoe for Usain Bolt with the ultimate objective of speeding up package delivery - a kind of cognitive myopia that misleads people into working at the atomic level over and over in the belief that it will be simpler. In fact, it's one-dimensional (in the sense taht you need to read and type everything out even as you hope around different parts of your code base) and reductionist to the point of becoming a distraction from the actual problem you are trying to solve.
Virtually every project of any substance starts out as a flowchart on a whiteboard or memo pad. The idea of flowcharts and pipelines are ubiquitous in production environments because they reflect the way we interact with the world. You don't start a new job at a new company by cutting a hole in the wall of your home and then building a vehicle from scratch to get to the company's office, you walk through the door and then ride a bicycle/car/bus/train to reach your destination without needing to re-engineer the whole thing from scratch.
Reading and writing are great when you don't know exactly what you want to learn or to say and you need to grope your way to ward it. When you do know, it's generally much easier and more useful to everyone else to use a picture or some sort of schematic diagram. You don't need to be Leonardo Da Vince to draw flowcharts, and thanks to the abundance of storage you don't need an infinite wall of whiteboards or learn origami to nest flowcharts. It's nested structures all the way down. You will get more done and not burn out as fast if you stop forcing yourself into a linear text-based paradigm just because you're used to it.
tl;dr Structure >> syntax