Comment Reducing software complexity is a high set goal... (Score 1) 178
...but it's good to try it out. The more the complexity grows the more work ist to be done when you want to upgrade things or simply fix an error. Take a look at a programming language as easy to read as e.g. ABAP/4. It's almost readable as a plaintext but still you can build extremely complex software.
If you have a IDE that allows you to abstract the coding from the semantic significance, it makes your code more easy to understand. If you have different levels of abstraction (like some diagrams in UML) and your IDE supports working in higher abstractions and not just viewing, you can build new things on a more abstract and therefore easier level.
But to achieve that either every project has it's own levels and definitions of abstraction levels or it has to be built in the programming language itself. But both possibilities will increase the complexity of the abstractions. So no easy going... ;)
If you have a IDE that allows you to abstract the coding from the semantic significance, it makes your code more easy to understand. If you have different levels of abstraction (like some diagrams in UML) and your IDE supports working in higher abstractions and not just viewing, you can build new things on a more abstract and therefore easier level.
But to achieve that either every project has it's own levels and definitions of abstraction levels or it has to be built in the programming language itself. But both possibilities will increase the complexity of the abstractions. So no easy going...
