IEML for software engineers
I am a software engineer. My interest for IEML is philosophical and maybe even a bit esoteric, but I’m also interested in its power from a purely engineering standpoint. Here’s my take on it.
To begin with, IEML is a language in its own sake; one of its own kind, too, however, since it has a universal scope. It stems from a long philosophical ambition to conceive of a language that is the language of the mind. Foremost, it is also a script through which we can not only describe ideas, things or concepts, but, as we are doing so, it gives us the power to understand and to discover more about the reality we are trying to model. This process, in which we are constantly re-evaluating our own assumptions about our personal ideas, is what makes IEML a bridging technology for humans to collaborate accross disciplinary boundaries and language barriers, almost without us ever noticing it.
As a software engineering tool, IEML is the technology for IT experts to create systems that are not only technically interoperable, but whose functionality will be expressed in the most generic way and which will allow for a whole new level of reusability. It has the potential to create a breakthrough in design pattern engineering aswell as in SOA software design. Imagine a world where Web Service descriptors not only expose method signatures but also the true meaning and scope of these methods in a way that is understandable by machines. IEML is the empowering technology for software engineers to exponentially grow our ability as a species to think collectively and, ultimately, to better understand the world we are living in.