This white paper introduces weaknesses of existing applications that led to the reflection "self-programming"

1. Self-programming introduction
White paper from adelrick Labs © July 2013
1
SELF-PROGRAMMING
INTRODUCTION
WHITE PAPER

2. Self-programming introduction
White paper from adelrick Labs © July 2013
2
Le Code de la propriété intellectuelle n’autorisant, aux termes de l’article L.112-5, 2° et 3° a),
d’une part, que les « copies ou reproductions strictement réservées à l’usage privé du copiste
et non destinées à une utilisation collective » et, d’autre part, que les analyses et les courtes
citations dans un but d’exemple et d’illustration, « toute représentation ou reproduction
intégrale ou partielle faite sans le consentement de l’auteur ou de ses ayants droits ou ayants
cause est illicite » (art. L. 122-4). Cette représentation ou reproduction, par quelque procédé
que ce soit, constituerait donc une contrefaçon sanctionnée par les articles L. 335-2 et suivants
du Code de la propriété intellectuelle.

3. Self-programming introduction
White paper from adelrick Labs © July 2013
3
Introduction
In this paper, we focus on the bottlenecks in enterprise software delivery caused by the
handoff from Information Office. Typically, the development team struggles to deliver
applications at the pace that the customers demand them. Agile practices have enabled
development teams to quickly create change. But manual processes, poor communication
between developers and operations, and inconsistencies between processes and tools prove
too error-prone for operations to deploy safely every release to production (sometimes even to
test, UAT, etc.). As a result, applications with interdependencies pile up, and organizations
are not able to keep up quickly with business needs, market trends, and customer demands.
Companies need a way to deploy changes at an accelerated pace while maintaining stability.
If company is not able to deliver software faster and minimize the risk, it may lose this
market.
Current applications limitation
There are what current applications do not have:
Requires manually pre-solving the problem and pre-programming the solution
Requires manually structuring the user interfaces
Any changes require new manually written code
Unable to share mode of reasoning
Require manually structuring the data
Can not infer new behaviors from huge input information
Conclusion
These weaknesses identified questioning the nature of existing applications, but also the
software engineering methodology. adelrick’s company has addressed this issue. This
reflection has founded adelrick’s technology and a new programming paradigm: the “Gestalt
Programming”. The "Gestalt Programming" was inspired by the behavior of human beings,

4. Self-programming introduction
White paper from adelrick Labs © July 2013
4and relies on a set of technologies of Artificial Intelligence to define a new programming
paradigm that enables an application to learn and produce other applications by itself.
The approach technology "adelrick", aims to address these challenges, allowing developers to
detach from repetitive development tasks, allow computer systems to automatically change to
the needs of the market to help manage and improve performance in a company.
In the next white papers we will present the concepts of "Gestalt Programming".