In 2025–2026, the speed at which code moves from a pull request to release became one of the key indicators of resilience for technology companies. Against the backdrop of growing development volumes, GitHub continues to track activity across pull requests and commits, while GitLab notes that teams lose hours every week due to inefficient processes, fragmented tools, and weak communication. As a result, the problem of code review has ceased to be a localized engineering delay. For businesses, it has become a matter of time-to-market: when changes remain stuck in approvals for several days, the product responds more slowly to customer needs, the team loses focus, and development velocity stops translating into actual delivery speed. Reducing the code review cycle from days to hours therefore requires not pressure on engineers, but a rethinking of processes: clear PR-flow rules, transparent ownership, timely notifications, and standardized communication among development participants.
In this context, Gleb Sinani’s professional experience at Autodesk offers a telling example of how process changes can directly influence the productivity of an engineering team. Working as a lead software engineer, Gleb focused on removing structural barriers that prevented the rapid delivery of software modules. His approach was based on the principle that high-quality engineering should not conflict with speed: long waits for review are often not a technical inevitability, but the result of suboptimal interaction within the team. As Gleb notes, “The main difficulty in large projects often lies not in the volume of functionality, but in the complexity of communication within the PR flow. When we begin working, our goal is to create an environment where every engineer understands the standards for notifications and ownership, making it possible to shorten the path from writing code to deploying it.”
The main stage of the changes implemented by Gleb at Autodesk was the transformation of pipelines and a rethinking of how the team worked with code. To reduce the code review cycle from three days to less than one business day, he carried out a comprehensive refactoring of the pipeline structure. Gleb changed code packaging strategies and decomposed two primary execution paths, which helped reduce infrastructure complexity. This technical decision allowed the team to move away from monolithic approval processes toward a modular approach, in which changes pass through CI/CD tools with predictable response times. “Reducing review time to less than one day at Autodesk was the result of rebuilding the norms of team interaction,” Gleb explains. “We introduced standards that allow engineers to work with decomposed modules, thereby minimizing downtime and ensuring system stability without compromising the quality of the final product.”
Implementing such changes requires a leader who can clearly justify the need for reorganization. Gleb Sinani emphasizes that resistance to change in engineering environments is often driven by concerns that quality may decline when teams move toward faster releases. In practice, however, the opposite is true: when the process becomes transparent, engineers pay closer attention to the quality of each iteration, because the risk of accumulated errors within modules is minimized. “Code quality does not suffer from speed; it suffers from unmanaged change,” Gleb says. “When the review process is transparent, and CI/CD pipelines are configured clearly, the level of engineer ownership within each task only increases, which strengthens architectural reliability over the long term.”
Special attention was also given to standards for team interaction. At Autodesk, Gleb faced the challenge of synchronizing the work of development groups whose different approaches to notifications led to lost time. The creation of a unified communication standard made it possible to formalize expectations for every stage of review. Instead of spontaneous interaction, the team introduced a structured flow with clearly defined priorities and review criteria. This allowed the team to move from a “firefighting” mode to planned development of complex system modules aligned with the company’s business requirements.
The integration of new code packaging strategies also produced a direct economic effect. Reducing infrastructure complexity through the decomposition of execution paths freed up computing resources that had previously been spent on processing redundant CI/CD operations. At Autodesk’s scale, where design tools require substantial computational power, this kind of optimization directly affects operating costs. As Gleb notes, “Technical optimization always has a business dimension. Removing unnecessary stages from the pipeline is not only a way to save cloud resources, but also a contribution to reducing the time it takes to bring a product to market.”
Moreover, Gleb Sinani’s experience demonstrates how a lead software engineer can serve as a catalyst for changes that reshape the entire team’s working model. By optimizing processes, he creates conditions in which developers can see the results of their work more quickly. This fosters a culture of continuous improvement, where every participant is motivated to look for new ways to accelerate releases. Sinani actively applies this approach in mentoring, showing colleagues that architectural mastery is not about creating complex systems, but about making them simple to manage and operate.
What distinguishes Gleb’s expertise is that he views the development process as an integrated system of business alignment. Unlike standard practices, where code review remains a formal control stage, his approach turns the process into a tool for maintaining architectural clarity. Gleb Sinani focuses on ensuring that API architecture and modular structure allow engineers to work autonomously, reducing dependence on long waits for approvals. His experience is valuable for other teams because it proves that accelerating releases does not require additional resources; it requires process optimization and the introduction of standards that make the software lifecycle transparent.
Summarizing Gleb Sinani’s work with engineering processes at Autodesk, it is worth noting that his contribution to engineering practice lies in a disciplined, systems-based approach to development. His ability to translate complex technical changes into measurable results underscores the role of an expert capable of building processes oriented toward long-term success. Gleb demonstrates in practice that technological leadership in 2026 is built on a precise understanding of the relationship between architectural decisions and product release speed. Thanks to his approach to CI/CD and team interaction culture, work on large-scale platforms becomes more efficient while preserving the high reliability standards expected by professional users around the world.
