Petes Linkedin Blog

   This blog post is Unfiltered    As a designer, it’s difficult to balance the scale of initiatives: Design too small, and nobody is excited or can understand the direction things are going. Start too big and everyone on the team may be too intimidated to start. ThinkBIG is a way of utilizing designers’ natural skillset to balance the iterative nature of engineering with the visionary nature of design. Here are 5 signals that you should switch up your style and Think Bigger: 1) Every milestone is spent only prepping the next Signal We’ve all been there. The next milestone planning issue is starting to get filled out and you, the designer, are realizing how many issues need design in order to be ready. As the priorities shift, you know the last two weeks of this milestone will be spent desperately trying to design mockups for engineers to start working on days later. I like to call this “Feeding the sharks”. It describes a certain level of panic some designers ...

Infuriating, facepalm-inducing, but with an intensely satisfying payoff when (if!) you figure them out, bugs are an unavoidable part of being a developer. When senior developer evangelist Brendan O'Leary shared with us this amusing story about a "bug" he solved in a previous role, we knew we had to ask you about your most elusive bugs. Now we're sharing some of the best bug stories with you, along with some lessons. Brendan's example was in fact not a bug at all, but actually the result of an employee resting their purse on the keyboard. This is the first lesson:  Debugging tip 1: It might not be a bug at all A surprising number of "bugs" actually have nothing to do with code. One of the first principles of debugging is to reproduce the bug to get started. If you can't do that, it could be a sign that, er, human factors are at play. Consider this example from @MrSimonEmms on Twitter: I once spent an entire day chasing down an error because...

Today we are releasing versions 13.10.1, 13.9.5, and 13.8.7 for GitLab Community Edition (CE) and Enterprise Edition (EE). These versions contain important security fixes, and we strongly recommend that all GitLab installations be upgraded to one of these versions immediately. GitLab releases patches for vulnerabilities in dedicated security releases. There are two types of security releases: a monthly, scheduled security release, released a week after the feature release (which deploys on the 22nd of each month), and ad-hoc security releases for critical vulnerabilities. For more information, you can visit our security FAQ . You can see all of our regular and security release blog posts here . In addition, the issues detailing each vulnerability are made public on our issue tracker 30 days after the release in which they were patched. We are dedicated to ensuring all aspects of GitLab that are exposed to customers or that host customer data are held to the highest security standar...

It's been an exciting year for the GitLab for Education Program! We hit 2 million all-time seats issued, we connected with many of our Program Members through coffee chats, on issues, in our customer reference program, and through our GitLab for Education Program 2020 Program Survey . Through these conversations and the survey, you've shared with us your successes and some of your challenges with bringing the DevOps transformation to your campus. Our survey yielded some great insights about your journey, which have inspired the iterations to our solutions for education (which you can read about below). Specifically: GitLab is used extensively across the entire educational institution Adoption extends well beyond typical Computer Science departments into many different academic departments as well as administrative departments such as information technology and services. Departments ranged from natural and social sciences, to medical fields, nearly every time of engineering, ...

By moving to the cloud engineering teams can accelerate innovation and scale resources across an organization. The ease of access and reduced infrastructure costs that comes with moving to the cloud is a direct result of using a platform that easily integrates your data and keeps it secure yet accessible. Gitlab.com, the cloud (SAAS) platform for GitLab, modernizes data platforms to leverage new applications and advances end-to-end software delivery. GitLab partners with other best-in-class cloud companies so your teams can use tools that best align with your team's DevOps ecosystem. Application development requires speed and iteration, making seamless collaboration a necessity to deliver real business value. GitLab embraces connecting all phases of the software development lifecycle (SDLC) in a DevOps ecosystem that fuels visibility, collaboration, and velocity. How to use GitLab with Atlassian's Jira We know that many companies have been using Jira for project management, a...

We know that we can iterate faster when we innovate together. We want to highlight how you make GitLab better every day by contributing to our open DevOps platform, by suggesting improvements, submitting bug fixes, and contributing features. You contribute around 300 merge requests to GitLab each month. Just look at last month's release for a multitude of examples – a reminder that everyone can contribute . Achievement unlocked: having NASA contribute directly to your codebase. Open core ftw. https://t.co/qcnu8jhQuR — Brendan O’Leary (@olearycrew) February 22, 2021 Roger Meier, principal key expert and service owner of code.siemens.com from Siemens IT explains, “If we want to have new features, we contribute them to GitLab.” An open DevOps platform gives you visibility into security and beyond Working in the open presents unique security challenges (you can read about how we prevent security fixes from leaking into our public repositories ), but we’re proud of how taking...

GitLab acquired Peach Tech , the industry leader in protocol and API fuzz testing, last year. We were thrilled to release API fuzz testing as part of our 13.4 release . Since then we’ve made tons of improvements, such as adding Postman support and supporting runtime value overrides , and we've received great feedback. We’ve also heard the questions about the Peach protocol fuzz testing capabilities and what is going to happen to them. Today, we are incredibly excited to announce that we are releasing the core protocol fuzz testing engine of Peach as GitLab Protocol Fuzzer Community Edition , and it's open source! This edition has many capabilities previously only available with a commercial Peach license. It contains the engine to run and orchestrate fuzz tests as well as the pieces needed to define your own protocols. This is a major gain for the open source community Previously, the only way to get access to many of these tools was to pay for the commercial version of P...

GitLab 13.10 is now available! This month, we’ve focused on scalability and manageability across the product so you can iterate and innovate faster, with greater security and fewer headaches. 13.10 offers Admin Mode to protect your data from human error, Geo package integrity verification to improve Disaster Recovery, vulnerability management automation to apply efficiency and consistency to security processes, and—as always—a ton of fantastic contributions from the wider community. These are just a few of the 40+ new features and improvements in this release. Scaling DevOps Managing a growing DevOps org is challenging. GitLab 13.10 introduces several new features to automate routine tasks, boost your efficiency, and grow DevOps within the organization without losing control. Admin Mode protects sensitive operations and data from accidental errors by allowing administrators to toggle between admin and user privileges on the same account. We’ve leveled up support for DORA metrics, t...