June 2017 Summaries

Dimitrie, a GitLab team member, embarked on an ambitious journey to visit colleagues across Europe and Asia, inspired by the company's "Travel to visit GitLab team-members" policy and the "visiting grant." His travels included meeting six colleagues in five cities spanning four countries, driven by the unique opportunity to connect with teammates in person, as experienced during a GitLab summit in Cancun. This journey began in London and continued through Mumbai, Pune, Goa, Siem Reap, and finally Taipei, where he connected with GitLab colleagues, explored local cultures, and navigated the challenges of working remotely while traveling. Throughout his trip, Dimitrie utilized a detailed planning spreadsheet, incorporating automation features for efficiency, which facilitated the coordination of schedules, travel logistics, and expenses. His encounters highlighted the diverse cultures and working styles of his colleagues, enriching his perspective and reinforcing the value of GitLab's core values like collaboration, results, and transparency. Dimitrie's experiences were not only personally rewarding but also served as a learning opportunity for others, as he contributed tips and insights to the GitLab handbook to support future remote work and travel endeavors.

At VueConf 2017 in Wrocław, Poland, GitLab shared its transition from CoffeeScript to ECMAScript 6 and its integration of Vue.js into its tech stack, emphasizing the creation of small Vue applications rather than a complete rewrite. The conference, organized by Monterail, featured insights from the Vue community and highlighted GitLab's approach to Vue application architecture, including state management through a store and service, and the use of vue-resource for API communication. GitLab employs a mediator to optimize network calls and share state between applications. Future plans involve standardizing Vue code with a style guide, creating reusable components, implementing a linter, and exploring Vuex for complex coding needs. The event underscored the collaborative and open spirit of the Vue community, with contributions from sponsors and organizers.

GitLab has evolved from a version control system to a comprehensive DevOps platform that allows users to manage the entire software development lifecycle, from idea generation to production, without the need for multiple tools. It holds two-thirds of the market share in self-managed Git hosting, with its continuous integration (CI) system being the most popular next-generation option. The integration of CI/CD within GitLab offers time and resource efficiency, enabling developers to detect and address issues early, as demonstrated by companies like Ticketmaster. GitLab's future direction includes Auto DevOps, which aims to automate the DevOps process with features like Auto Create, Auto Build, Auto CI, Auto Deploy, and Auto Code Quality. This initiative seeks to streamline cloud-native development by eliminating the need for manual tool setup across projects, leveraging community contributions and customer feedback to enhance the platform's capabilities.

Developers face significant challenges in meeting deadlines due to communication breakdowns and cultural issues within teams, as revealed by a Global Developer Survey. The survey highlighted that unclear direction and unrealistic deadlines are major obstacles, affecting nearly 47% and 21% of developers, respectively, and leading to premature code releases. Traditional linear development processes contribute to these issues by creating a disconnect between decision-making and execution teams. To address these challenges, adopting DevOps practices, such as working on smaller, iterative releases and forming cross-functional teams, can foster better collaboration and clearer communication. By involving all stakeholders early and throughout the development process, teams can better manage expectations, align motivations, and ensure realistic timelines. Encouraging collaboration within these cross-functional teams is crucial, as it brings diverse perspectives and expertise into the decision-making process, ultimately leading to more efficient and effective project outcomes.

Shortening the conversation cycle in feature development can significantly expedite shipping times, and this process begins by measuring cycle time to identify delays from idea inception to production release. Implementing minimum viable changes by breaking down ambitious projects into smaller, manageable pieces allows for quicker iterations and continuous improvement. Engaging gatekeepers such as stakeholders, security experts, and product managers early in the process helps prevent bottlenecks and ensures quality and security before production. Encouraging team members to embrace releasing unpolished features can be challenging but offers advantages such as faster responsiveness to market changes and enhanced motivation through frequent feedback. Adopting these practices, rooted in the principles of Conversational Development, can lead to tangible improvements in development workflows.

The text provides strategies to prevent burnout for employees, especially those involved in on-call rotations, by discussing the stages of burnout—caution, warning, danger, and emergency—and offering practical tips to improve on-call shifts. It emphasizes the importance of ensuring readiness before a shift, utilizing collected data to improve processes, choosing effective tools for scheduling and data aggregation, conducting controlled incident response drills, and involving code authors in the on-call rotation. It also highlights the significance of setting better schedules, encouraging vacations, and selecting appropriate shift lengths, such as 8-hour, 12-hour, 24-hour, or week-long rotations, based on team needs and capabilities. By proactively monitoring and adjusting schedules, teams can reduce stress and enhance overall efficiency, ultimately fostering a healthier work environment.

GitLab fosters collaboration and a DevOps culture by implementing strategies that encourage team members to contribute across different areas, including documentation, configurations, and tests, not just source code. By using version control and merge requests, the company creates an environment where suggestions and improvements can be made without fear, making documentation a collaborative, living document. GitLab's inner sourcing approach allows team members to access and contribute to projects beyond their own, promoting shared learning and avoiding work duplication. The company also emphasizes impersonal code reviews, encouraging input with constructive language to improve code quality without intimidation. These practices remove barriers to contribution, facilitating a culture of open collaboration and continuous learning.

GitLab embarked on a project to identify user personas by conducting a survey that combined open-ended and closed-ended questions to explore user motivations and experiences. The survey was designed to mitigate bias by shuffling answer options and was refined through internal testing to ensure clarity and intent. Advertised on GitLab’s platforms, the survey attracted over 500 responses from engaged users, although it was acknowledged that this sample size might not fully represent GitLab’s vast user base, introducing potential selection bias. Analysis of the responses highlighted both strengths and gaps, prompting further research to address underrepresented user groups. The initial personas have been added to GitLab's handbook but remain a work in progress, with ongoing adjustments based on additional user feedback from interviews, testing, and future surveys. Users are encouraged to participate in "GitLab First Look" to contribute further insights.

Ticketmaster's mobile team aimed to achieve weekly releases, which they successfully implemented for both Android and iOS apps since February, leading to improved fan experiences and product quality. Initially, the team faced challenges with their Jenkins-based CI pipeline, which was slow and cumbersome, ultimately prompting a switch to GitLab CI. This transition, facilitated by the use of Amazon ECR for Docker container management, significantly reduced build times to under eight minutes and improved the team's ability to measure and enhance code quality. The move to GitLab CI enabled faster cycle times, smaller change sets, and better crash-free rates, allowing the team to focus more on product improvements and swiftly integrate new SDKs, positively impacting store ratings and user satisfaction. As a result, the team now spends less time waiting for builds and more time innovating, establishing GitLab CI as a vital component in their successful transition to a modern, efficient CI pipeline.

In the fast-paced world of software development, the emphasis on releasing new features quickly has prompted teams to innovate their development processes while maintaining high quality and security standards. By integrating security as a foundational aspect from the beginning of the development lifecycle, rather than as an afterthought, teams can address vulnerabilities early on, reducing risks and fostering a more secure environment. Key practices include making smaller, frequent changes to facilitate quicker code reviews and involving stakeholders, including security experts, early in the process to anticipate problems and streamline development. Additionally, pushing code into staging or test environments early and leveraging community-driven efforts like bug bounty programs can further enhance security and quality assurance. These strategies, as discussed by GitLab's Victor Wu and Brian Neel, promote a more efficient development cycle that balances speed with security and quality.

In a conversation with Brandon Foo, GitLab's CEO and Co-founder Sid Sijbrandij shares insights into the company's growth strategies, product development approaches, and funding decisions. During its early stages, GitLab focused on engaging with users where they were, transitioning from attracting initial attention to addressing user feedback for improvement. Their product strategy involves a balance between introducing new features and enhancing the adoption of existing ones, with an emphasis on user utility and feedback. Sijbrandij discusses the importance of visionary innovation alongside customer-driven development, highlighting that leadership should focus on long-term company improvement while meeting current customer needs. On funding, he reflects that external capital was essential to attract top talent by offering stock options, which was crucial for market competitiveness. Reflecting on GitLab's evolution, Sijbrandij notes that launching GitLab.com earlier than ideal led to challenges in user experience, and he emphasizes prioritizing user satisfaction over sheer numbers.