Sourcegraph

“Lyft teams are constantly innovating and building new systems, necessitating decomposing and migrating off of older ones. Sourcegraph gives us the ability to search for and refactor references to deprecated services, libraries, URL patterns, and more across our 2000+ repositories, and the confidence that we're not leaving anyone behind. Sourcegraph makes it easy to survey and understand existing use cases to make sure we build the right thing.”

“During our decomp efforts, we also spent time to refactor our APIs. Many of these APIs were undocumented and lacked a formalized contract. With the help of Sourcegraph, we were able to quickly look at all clients of an API and remove unused attributes that lived in different repositories, ultimately simplifying our APIs and speeding up developer iteration time.”

“There's all these little hidden things that tax the velocity of the teams," Hodge said. "Earlier this month I was using Sourcegraph to find code and things we needed to replace, related to updating our build system, and we've seen an improvement in the build times as a result. But I feel like the summation of all these little things actually adds up to way more than just speeding up the build time.”

“On average, I'd say that for every automated merge request that we're able to merge we save an hour. That's a rough but conservative estimate. It shows, though, that if we are doing several thousand automated merges in a year, we're saving several employee's worth of time.”

“If I can reduce the amount of work a product team has to do by 90%, that is a huge win. Not only do they have to do less work — we're asking them to spend 10 minutes on a code review as opposed to spending the next six hours doing this change — they also don't have to spend time figuring out how to prioritize the different requests they're getting.”

“Sourcegraph helped me answer a question in like 5 seconds flat this afternoon. Normally I probably would have bugged a bunch of people, but the overview of "here is that snippet, and the list of repos using it" made it self-served.”

“If I'm developing code for a library that might draw charts, for example, we don't want 30 different ways to draw a chart at FactSet. With Sourcegraph, I can search the code to find other chart examples, and simply copy the code. This saves us time and ensures consistency.”

“For developers, Sourcegraph is a must-have tool一we need it at arm's length at all times.”

“With Sourcegraph, we were able to make a smooth transition from Perforce to GitHub.”

“We are developing software faster than ever, with aggressive schedules, and across boundaries. Things that used to be worked out in a closed room now need to be done while teams are spread out across the globe. Sourcegraph is essential in this environment, and I can't imagine being proficient at my job without it.”

“When implementing a feature and testing an API, we use Sourcegraph to go through the API and how it's implemented, see different parameters, read through the code around that API, and understand it better so that we can be better testers. If there are bugs, it's easy to understand the conditions around the error message and give meaningful feedback to our developers.”

“If I want to have a dialogue with a developer on a different team, it's as simple as pulling up Sourcegraph and walking through the code.”

“Before Sourcegraph, each of our teams was siloed. Developers could understand their own codebase, but it was difficult for them to see and understand other team members' code.”

“The quality of the Sourcegraph UI and its code intelligence are two game-changer features for us. It's like having an online IDE for browsing code.”

“The feedback we received was overwhelmingly positive. We had employees saying 'I've dreamt of a tool like Sourcegraph!', 'Please buy it!', 'It saved my life!', 'It literally saved me hours per day!' We're thrilled that it's given us the ability to make our developers happier and more productive in their roles.”

“At Criteo, developer happiness is our top priority—not just productivity. We want to tackle the things that developers see as hurdles in their day-to-day life. By providing them with the right tools, like Sourcegraph, we've found that increased productivity is a natural byproduct.”

“When looking for alternatives, the general consensus was 'If you're a giant like Google, you can simply build your own code search engine. If that's not you, then buy Sourcegraph.”

“Before Sourcegraph, we were struggling to search code in an accurate and timely manner. The legacy text-based search we relied on had security issues, and its performance was poor in terms of the quality of searches and response times.”

“We take security very seriously, and building and maintaining trust with our customers is incredibly important. Cody enables us to not only leverage technology that enables productivity but also keeps us secure.”

“One of the reasons we felt confident moving forward with Cody is because it runs on Amazon Bedrock. It integrates well with our existing cloud infrastructure. We must have full control over our data and environment to keep our customer data safe.”

“It wasn't just suggesting random pieces of code; it generated boilerplate code based on our internal SDKs and frameworks. It was a good signal we were on to something powerful.”

“Our mission is to be the most trusted crypto platform. Maintaining a high security bar while innovating is essential to earning and keeping that trust.”

“I really can't express how blown away I am with Cody. I can't go back to... whatever it was like before. I use Cody every day, all day long. No matter what I write, Cody helps improve it and it goes way beyond coding in some specific language, you can make Cody explain things to you every step of the way. Really, this is it, the future of coding.”

“It's not just about time savings. It's about how you're able to spend your time.”

“If you haven't yet asked Cody, don't ask me.”