devops, technical debt, GitLab, Duck Conf 2026, IT architecture, Michelin, software development, self-hosted platforms, team collaboration, scaling challenges ## Introduction The rapid evolution of technology demands that organizations adapt quickly to maintain a competitive edge. At Duck Conf 2026, industry leaders gathered to discuss the pressing challenges they face in the realm of DevOps, particularly when it comes to managing technical debt. During the conference, Adrien Gooris, an IT architect at Michelin, and Lucas Drago, tech lead of the Factory team, shared their insights on scaling a self-hosted GitLab instance from a few hundred to thousands of users. Their journey was not without obstacles, as they grappled with the accumulation of technical debt that threatened to overwhelm their progress. This article delves into their experiences and the strategies they employed to successfully navigate these challenges. ## Understanding Technical Debt ### What is Technical Debt? In the world of software development, technical debt refers to the shortcuts or compromises made during the coding process that lead to more complex or inefficient solutions down the line. While it can sometimes provide immediate benefits, such as faster deployment or quick fixes, it often results in greater challenges that require time and resources to address later. Organizations like Michelin must continually balance the need for speed with the management of technical debt to ensure long-term sustainability. ### The Impact of Technical Debt on Organizations As organizations grow, their systems must evolve in tandem. For Michelin, the challenge of scaling their GitLab instance was compounded by the technical debt that had accumulated over time. With a self-hosted platform supporting thousands of users, the stakes were high. The longer technical debt remains unaddressed, the more it can impede innovation, slow down development cycles, and lead to increased frustration among team members. ## The Journey of Scaling GitLab ### Initial Challenges Adrien Gooris and Lucas Drago painted a vivid picture of their initial challenges during their presentation at Duck Conf 2026. When they embarked on their journey to scale GitLab, they faced a myriad of technical issues stemming from legacy code, outdated dependencies, and inefficient workflows. These challenges not only hindered their progress but also raised concerns about the reliability and performance of their platform as user demands grew. ### Strategies for Overcoming Technical Debt To combat the inevitable technical debt that threatened to derail their efforts, Gooris and Drago implemented several key strategies: #### 1. Prioritization of Tasks One of the first steps in overcoming technical debt was the prioritization of tasks. By identifying the most critical areas that needed immediate attention, the team was able to allocate resources effectively and ensure that they were addressing the most pressing issues first. #### 2. Incremental Improvements Rather than attempting to tackle all technical debt at once, the team adopted an incremental approach. By making small, manageable changes over time, they were able to gradually improve the platform without disrupting ongoing development activities. This method allowed the team to maintain momentum while systematically addressing their technical challenges. #### 3. Continuous Learning and Adaptation The journey of scaling GitLab was not static; it required continuous learning and adaptation. Gooris and Drago emphasized the importance of fostering a culture of learning within their team. By encouraging team members to share insights and experiences, they were able to collectively identify solutions to emerging challenges and refine their processes. ### The Role of Collaboration in Scaling Efforts Collaboration played a crucial role in Michelin's efforts to scale their GitLab instance. Gooris and Drago highlighted how cross-functional teamwork enabled them to break down silos and foster open communication. This collaborative environment allowed for the sharing of knowledge and best practices, ultimately leading to more innovative solutions to technical challenges. ## Lessons Learned from Duck Conf 2026 ### Embracing Change One of the key takeaways from Gooris and Drago's presentation was the necessity of embracing change. As technology continues to evolve, organizations must remain flexible and open to new ideas. The ability to pivot and adapt is crucial for overcoming technical debt and successfully scaling platforms. ### Investing in the Future Investing in the future means setting aside resources and time to address technical debt proactively rather than reactively. Organizations should view this investment as a vital component of their long-term strategy, as it ultimately leads to enhanced productivity and a more stable platform for users. ### Building a Resilient Team Lastly, building a resilient team is essential for navigating the complexities of technical debt. Encouraging an environment of support, collaboration, and continuous learning fosters a culture where team members feel empowered and equipped to tackle challenges head-on. ## Conclusion The experiences shared by Adrien Gooris and Lucas Drago at Duck Conf 2026 serve as a valuable reminder of the importance of addressing technical debt in the pursuit of scaling DevOps platforms. By prioritizing tasks, implementing incremental improvements, fostering collaboration, and embracing change, organizations like Michelin can successfully navigate the challenges of growth while ensuring a robust and efficient platform for their users. As the tech landscape continues to evolve, these lessons will remain relevant for teams striving to build resilient and scalable solutions in an ever-changing environment. Source: https://blog.octo.com/duck-conf-2026-cr-a-l'epreuve-de-l'echelle-surmonter-la-dette-technique-et-les-defis-d'une-plateforme-devops