February 2025 Summaries
4 posts from Sourcegraph
Filter
Month:
Year:
Post Summaries
Back to Blog
Context retrieval is a pivotal component in transforming large language models (LLMs) into effective AI coding assistants by enabling them to provide responses grounded in a specific codebase. This process involves the context engine, which retrieves and ranks relevant snippets of code or text to enrich an LLM's understanding, allowing it to deliver precise, context-aware answers. The context engine functions through a two-stage process of retrieval and ranking, utilizing diverse techniques such as keyword searches, code embeddings, and graph-based analysis to gather potential context items from various sources like code repositories and documentation. The ranking stage then refines this selection to ensure that only the most pertinent information fits within the token budget constraints, ultimately enhancing the LLM's response quality. Evaluating this system poses challenges due to the lack of ground truth data and the complexity of user interactions, but overcoming these hurdles is crucial for developing AI tools that can significantly boost developer productivity by offering tailored, accurate assistance.
Feb 20, 2025
2,113 words in the original blog post.
Sourcegraph 6.0 introduces a unified user interface that integrates the world's leading large language models (LLMs) with a comprehensive knowledge graph of code, enhancing the way users search, understand, and create code. This update features a new chat experience that allows users to perform keyword searches and receive LLM-powered responses, all from a single entry point, accessible across platforms like VS Code, JetBrains IDEs, or the web. Users can request either a code search or an LLM response with their initial query, and use code search results as context for follow-up queries. Over time, the platform plans to introduce more advanced code-grokking agents and enhanced search capabilities to further support the software development lifecycle. Sourcegraph Enterprise customers upgrading to version 6.0 will gain immediate access to these new features, while Enterprise Starter customers will also have access, albeit with some limitations for Cody Free or Cody Pro users due to the lack of indexed codebases. Further information and opportunities for feedback are available in the documentation and on Discord.
Feb 05, 2025
329 words in the original blog post.
Sourcegraph has introduced the Enterprise Starter plan, designed for growing development teams of up to 50 developers, offering advanced code search and AI capabilities for $19 per user per month. This self-serve plan facilitates access to features such as code search, AI-enhanced chat, a prompt library, and multi-repo context capabilities that support up to 100 GitHub repositories and 5GB of storage, with the option to expand storage with additional seats. The plan includes Cody, an AI coding assistant that integrates with popular IDEs like VS Code and JetBrains, providing tools like autocomplete and agentic chat. These features aim to streamline development workflows by enabling precise code searches, context-enhanced communication, and reusable prompt sharing across teams, ultimately promoting efficiency and collaboration in software development processes.
Feb 05, 2025
777 words in the original blog post.
Cycle time is a crucial metric in software development that measures the time taken from when a developer begins coding to when the code is deployed in production, providing insight into the efficiency of the development process. It differs from lead time, which starts when a request is made and includes planning phases. Cycle time is actionable and reveals bottlenecks in stages like coding, review, testing, and deployment, enabling engineering teams to optimize these phases for improved efficiency. Industry benchmarks, such as those from the State of DevOps Report, categorize performance levels from elite teams with minimal cycle times to low-performing teams with extended durations. Shorter cycle times are advantageous as they allow faster feedback, better responsiveness to user behavior, and improved team morale. To reduce cycle time, teams should identify and address bottlenecks, optimize code review processes, streamline CI/CD pipelines, and limit work-in-progress. Effective measurement and analysis of cycle time, possibly aided by tools like Sourcegraph, can lead to significant improvements in development speed and productivity, offering a competitive advantage in fast-paced markets.
Feb 02, 2025
2,655 words in the original blog post.