What is the main problem with the current approach to code management? - Lack of XP practices leads to frequent errors and low code quality - Debugging only in production - No change management - No centralized configuration management - Insufficient test automation - Inefficient module integration

The main problem with the current approach is the lack of a systematic and modern approach to development and maintenance of code, which leads to low quality, a high likelihood of errors, and difficulties in support.

Problem analysis:

• Lack of implementation of XP practices (such as pair programming, continuous integration, refactoring) results in accumulated technical debt and frequent errors.
• Debugging only in production — extremely risky, as errors are detected too late, which can lead to downtime and negative impact on users.
• Change management is absent — no version control, code can be changed without approval, leading to conflicts and unpredictable behavior.
• No centralized configuration management — complicates deployment and support, increases the risk of errors due to inconsistent settings.
• Insufficient test automation — lack of coverage tests reduces confidence in stability and complicates making changes.
• Ineffective module integration — modules interact poorly, leading to errors and complicating system development.

As a result, the approach does not support DevOps and Agile principles, which negatively affects product quality and development speed. It is necessary to implement automation practices, version control, testing, and configuration management to improve reliability and efficiency.