For a programmer who has just completed his training, it is normal to be idealistic. Find "ideal" names of variables, "ideal" names of functions, build an "ideal" application architecture, "ideal" relationships with customers according to an "ideal" development plan. The world of "idealization" of programming is very fragile and breaks with the first shock with serious commercial projects. For the programmer, this is a new stage of development, seeking the balance between the effectiveness of its code and the ever-changing business requirements.
The concept of "idealization" for each specialist is individual, but it is important to understand that there are no serious projects written "ideally", even from the point of view of a professional who wrote the code. There are successful solutions, an architecture that can support many changes, but in any project, there is always a site that can be improved, from one point of view or another.
This problem concerns not only the technical field, but also many other areas of human activity - economics, politics, marketing and other "idealized" specialties at the training stage. The term "idealization" in this case refers to reference models that give a misunderstanding of reality to future scholars. This is the main value of work experience and interaction experience with people.
A common misconception is that many experts do not go beyond their "idealizations", they pursue their efforts to achieve perfection in inappropriate situations, lose their decision-making effectiveness, and display crude thinking when it is necessary to change the development vector, which can considerably increase the production costs of the product until the end of the project.
An example of the manifestation of the problem of idealization may be the use of design models when a programmer is unable to correct a model, feeling at the same time in error, as if he were breaking the unwritten law programming. Admittedly, the rules of the good tone exist and must be followed, while being based on reality. Effective programming requires an approach to reality rather than being within the bounds of reference thinking.
AZNResearch's specialists have experienced many professional metamorphoses, with a new awareness of the terms "ideal code", "development approach", "customer interaction", "marketing policy", which has brought together as much as possible true technical and social interactions in specialized environments. As experience grows, as the time needed to enter new areas of work diminishes steadily, there is real interest in the work generated by understanding the development process. We know what to do and how to find a common ground.