The technology behind GitHub’s new code search | The GitHub Blog
github.blog · 3,361 words · saved by 1 readers
A look at what went into building the world's largest public code search index.
The technology behind GitHub’s new code search - The GitHub Blog Timothy Clem · @tclem February 6, 2023 | 14 minutes Share: From launching our technology preview of the new and improved code search experience a year ago, to the public beta we released at GitHub Universe last November, there’s been a flurry of innovation and dramatic changes to some of the core GitHub product experiences around how we, as developers, find, read, and navigate code. One question we hear about the new code search experience is, “How does it work?” And to complement a talk I gave at GitHub Universe , this post give
related reading
- The technology behind GitHub’s new code search - The GitHub Bloggithub.blog
- Building a web search engine from scratch in two months with 3 billion neural embeddingsblog.wilsonl.in
- Fast regex search: indexing text for agent tools · Cursorcursor.com
- Why GitHub Actually Won | Butler's Logblog.gitbutler.com
- Training a Specialist Code Search Agent with turbopufferappliedcompute.com
- GitHub · Change is constant. GitHub keeps you ahead.github.com
- Regular Expression Matching with a Trigram Indexswtch.com
- Why We Built Our Own Background Agentbuilders.ramp.com
- GitHub - thesephist/monocle: Universal personal search engine, powered by a full text search algorithm written in pure Ink, indexing Linus's blogs and private note archives, contacts, tweets, and over a decade of journals.github.com
- How GitHub monopolized code hostinggraphite.dev
- How Cursor Indexes Codebases Fastread.engineerscodex.com
- Git's database internals V: scalability - The GitHub Bloggithub.blog