March 2018 Summaries

GitLab has undertaken a revamp of its color palette to address feedback regarding inconsistencies and quality issues in its user interface (UI). Recognizing that color is a crucial component of UI aesthetics and significantly impacts user perception, the team aimed to align the new palette with brand colors, reduce the number of similar hues, and ensure compliance with Web Content Accessibility Guidelines (WCAG) for contrast. The process started with evaluating existing color schemes, such as Open Color, but ultimately led to creating a custom palette tailored to GitLab's specific needs. This involved generating tints and shades of selected hues, ensuring clear contrast, and establishing a color priority system to guide users in selecting appropriate shades for UI elements. The goal was to enhance usability and accessibility while maintaining visual harmony. The initiative is part of a broader effort to refine GitLab's UI, with plans to update typography next, reflecting an ongoing commitment to improving user experience.

Jump Associates explores the distinct cultures of innovation across various companies, highlighting GitLab as an exemplar of rapid execution and high-efficiency innovation. GitLab, an open-source software company, operates remotely without a physical headquarters, employing over 200 people worldwide. Their unique approach involves valuing "boring solutions," prioritizing speed and efficiency over novelty, and maintaining transparency through their publicly available business strategy and comprehensive company handbook. GitLab's culture centers on rapid iteration, with monthly product releases and a strong emphasis on their core values, which guide decision-making and drive their competitive advantage. While GitLab's method of innovation may not suit every organization, it offers valuable insights for companies looking to enhance their own innovation processes by understanding and leveraging their unique strengths and values.

In response to community feedback, a revised version of the Compensation Calculator was released in January 2018 to better align employee salaries with market rates and ensure fairness across different regions. This updated formula uses the San Francisco market as a benchmark and incorporates factors such as rent indexes, level and experience factors, contract types, and country-specific adjustments to calculate compensation. Adjustments were made to account for geographical and market differences, including a minimum rent index to prevent significant pay disparities. The People Ops team reviewed and adjusted salaries based on this new iteration, which also facilitated discussions around career growth. Looking forward, the aim is to enhance the tool by including more countries, refining factors for specialization, and improving data accuracy in order to address pay inequality and promote transparency. Feedback from users is encouraged to further refine the calculator.

The complex and fragmented nature of today's DevOps toolchain, often referred to as the "DevOps tax," involves significant time and effort spent on integrating various tools necessary for application delivery, which hampers software innovation. In a webcast featuring Mark Pundsack from GitLab and Forrester's Christopher Condo, the discussion centered around this challenge and how IT leaders can mitigate it by streamlining their toolchains. The conversation highlighted the importance of digital transformation, emphasizing quick and high-quality value delivery to customers, and underlined the necessity of prioritizing customer experience to remain competitive. The webcast also touched on current DevOps trends like better tool and team integration, the critical role of containers, and the benefits of concurrent DevOps processes. To reduce the DevOps tax, best practices include optimizing CI/CD pipelines, creating integrated product teams, modernizing architecture with microservices, and minimizing integration points across the development lifecycle.

The 2022 Global DevSecOps Survey, capturing insights from over 5,000 DevOps professionals, explores job satisfaction and challenges within software teams, revealing that despite some differences, developers and managers often share similar perspectives. Managers generally have a rosier outlook, but both groups report issues such as resistance to change and unclear direction as significant challenges. The survey highlights that communication difficulties and cultural barriers can impede DevOps adoption, with suggestions like embedding team members across disciplines being seldom chosen due to organizational resistance. Developers emphasize the importance of mutual respect and tying communication improvements to broader cultural changes, such as aligning incentives with team rather than individual performance, to foster better collaboration and overcome miscommunication.

GitLab's UX team has embraced the use of epics to manage their iterative design process while maintaining a comprehensive view of the application. Epics, a concept derived from Agile methodology, allow the team to organize and track collections of related issues, such as the over 100 UX improvements tied to the merge request page. By creating a UX strategy template, the team outlines challenges, vision, focus areas, mission, activities, and measurements of success for each epic, facilitating clearer planning and execution. This approach aids in prioritizing issues, aligning them with the team's strategic goals, and adjusting priorities as new information emerges. Epics provide better visibility into UX priorities for other departments and support long-term planning across milestones. Future developments will enhance epics with features like labeling, discussions, and integration with roadmaps, offering a graphical overview of goals and deliverables.

GitLab, a company with over 200 employees, operates entirely without a physical office, conducting all meetings remotely, which initially seemed unproductive to some. However, firsthand observation reveals that remote meetings can be highly effective, even surpassing traditional in-person gatherings. Key elements contributing to this success include the use of video conferencing with everyone joining individually, ensuring equal participation and preventing in-room power dynamics, and a shared live agenda in Google Docs that encourages structured and deliberate communication. GitLab's practice of embracing multitasking allows participants to tune in and out as necessary without disrupting the meeting flow, making sure the right people are engaged at the right times. Tools like Zoom and Google Docs are crucial to this process, and while this approach works well for most meeting types, there are considerations about its efficacy for technical brainstorming sessions, where traditional whiteboards might be more effective. The author, Nolan Myers, who advises startups and has a background in organizational development, initially believed remote work might hinder productivity but now recognizes the potential advantages of well-executed video calls.

Working at GitLab has been a transformative experience for the author, who reflects on a journey marked by personal and professional growth over 19 months in a remote, diverse, and inclusive environment. The author highlights the importance of GitLab's core values, which include clear communication, gratitude, learning from failure, trust, and embracing diversity, and how these principles have positively impacted their approach to work and life. By adopting a prototyping mindset, the author has become more open to feedback and less afraid of making mistakes, allowing for continuous improvement. Additionally, the culture of trust and support at GitLab has empowered the author to overcome language barriers and build meaningful relationships with colleagues from around the world. The emphasis on diversity at GitLab, seen in its global hiring practices and inclusive benefits, has broadened the author's perspectives and reinforced the belief in equality. Overall, GitLab's unique culture fosters an environment where employees feel valued and encouraged to grow, making it an appealing workplace for those interested in joining.

GitLab manages on-call incidents for its distributed team by assigning production engineers to weekly on-call shifts, ensuring availability for critical alerts and infrastructure issues across multiple time zones. The on-call system is designed to follow the sun, minimizing disruptions during night hours, and engineers are encouraged to take time off after shifts that require out-of-hours responses. To prevent issues from being overlooked between shifts, a weekly 30-minute on-call handover meeting is held to review incidents from the past week, assess the need for further attention, and transition tasks to the next shift. This process is automated using a program called the on-call robot assistant, which compiles data from sources like PagerDuty, Grafana, and GitLab's own tools to generate comprehensive reports. These reports are publicly accessible, allowing for transparency and collaboration, and the on-call handover includes input from other group leads to address high-priority items for specific services.

Burnout is a prevalent issue among professionals working at startups, especially in remote environments, where the pressure to meet deadlines and the ease of overworking can lead to exhaustion and decreased job satisfaction. At GitLab, team members have shared personal experiences and symptoms of burnout, such as constant fatigue, decreased enjoyment in activities, diminished job performance, and strained relationships. To combat and prevent burnout, GitLab has implemented strategies such as setting clear work-life boundaries, taking regular vacations, knowing when to take breaks, and disconnecting from work outside office hours. The company encourages open communication about burnout, with team members advised to discuss their concerns with managers and hold each other accountable. GitLab has also incorporated resources and tips into their handbook to help recognize and mitigate burnout, fostering a supportive workplace culture that emphasizes the importance of mental and physical well-being.

The 2022 Global DevSecOps Survey, which gathered insights from over 5,000 DevOps professionals, highlights the ongoing challenges and trends in the software development landscape. Key findings reveal that unclear direction is a significant challenge for developers, while IT managers prioritize investments in continuous integration and delivery. The survey underscores the growing importance and adoption of DevOps practices, with a notable increase in productivity among teams that have embraced a clear DevOps culture. Additionally, the survey emphasizes the critical role of open-source tools in software innovation, as nearly all respondents acknowledge their importance. Conducted by GitLab, the survey involved a diverse group of software professionals worldwide, ensuring a representative sample with a focus on addressing gender imbalance among respondents.

GitLab.com is addressing a security vulnerability related to the feature allowing users to create new issues via email, which is managed by Service Desk using the @gitlab.com domain. An attacker could exploit this feature to perform unauthorized actions, impacting users who utilize the email issue creation, Reply by Email, and Service Desk functionalities. To mitigate this issue, GitLab is advising users to update their email aliases and domain whitelisting from @gitlab.com to @incoming.gitlab.com. The company plans to disable the use of @gitlab.com for these purposes by April 31, 2018, and will reject incoming emails sent to the old addresses. GitLab is actively reaching out to affected users to ensure compliance with these changes by April 17, 2018.

GitLab effectively supports Agile methodology by mapping its features to Agile artifacts, allowing for streamlined project management and efficient software development. The platform's flexible features, such as Issues, Tasks, Epics, Iterations, Issue Boards, and Burndown Charts, correspond to Agile elements like user stories, tasks, epics, sprints, product backlogs, and Agile boards, respectively. GitLab enables teams to manage tasks, prioritize backlogs, and visualize workflows, thereby enhancing collaboration and accountability. The platform's capabilities include robust metadata for issues, real-time updates, iteration management, and dynamic issue boards, which facilitate balanced workloads and effective task management. Additionally, GitLab's integration with CI/CD and Review Apps supports quality assurance and allows for the demonstration of features in various environments. This comprehensive suite of tools ensures that Agile teams can maintain seamless collaboration, adapt to risks promptly, and document retrospectives to track progress over time, ultimately transforming Agile delivery processes.

A recent survey within a Frontend team revealed that Visual Studio Code (VS Code) is the most commonly used integrated development environment (IDE), prompting the development of a GitLab extension to enhance productivity by minimizing context switching. Initially created to display issues and merge requests from GitLab directly within VS Code, the extension quickly gained popularity, receiving positive feedback and over 5,000 installations in a month. It offers features such as viewing and managing pipeline statuses, searching and interacting with issues and merge requests, and performing GitLab-related actions without leaving the VS Code interface. The extension's success led to frequent updates and continued recognition on the Visual Studio Marketplace.