Sourcegraph

“Unlike other tools, Sourcegraph doesn't just search for keywords, it searches for regular expressions. This familiar query language allowed us to zero-in on exactly what we wanted and filter out false matches.”

“One of the most daunting things as a junior engineer is working on a large, existing codebase. There is always a ton of domain knowledge about that code that's restricted to the people who wrote it, no matter how well it's documented. There are always nuances that only the code authors know. But if developers know how to prompt Cody, Cody can find context and explain the code to them.”

“Something that would've taken me multiple dev days was done in an hour with Cody. Cody can generate a template for a test, and then I can prompt it to make adjustments to get the test to cover exactly what I'm looking for.”

“Generating unit tests, by far, is my number one favorite feature and time saver for Cody. I can spend my brainpower somewhere else instead of spending it figuring out how to write tests.”

“One of the places we're thinking of using Cody is connecting it with other initiatives. For example, in DevX, we have one program to improve code coverage: setting goals for all teams to achieve certain coverage with unit tests. We see a direct correlation with Cody here since Cody has proven adept for creating tests and improving code coverage.”

“Cody's ability to switch backends, from Claude to GPT, is very attractive to us. This is a fast-moving field, and we see updates to LLMs constantly, so having a tool that can react to new LLMs quickly is important to us.”

“We run our own GitLab instance within our own data centers, and Sourcegraph works seamlessly with it. That made signing up for Cody easy.”

“When choosing a coding assistant, we prioritized DLP [data loss prevention] and assurance of the security of our intellectual property. Cody worked seamlessly with the systems we already had in place.”

“That's hopefully something customers will remember us for,”

“We used Sourcegraph contexts to see specifically where a service was at any given point in time,”

“I can't imagine the pain of having to do that either with grep or OpenGrok,”

“That took almost less than five minutes,”

“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.”