William Bezuidenhout

[William Bezuidenhout @BurmudarFTL]

@nicolaygerold Guessing this is your office now

[Erik Seliger @erikseliger]

@Sourcegraph Once on a WYSIWYG platform, our new engineer-written Changelog is now a beautiful and simple app.
Our engineers own the storytelling of what they ship and write in markdown.
Very agent friendly.

Btw, lots of things shipping this week, check it out!
https://t.co/NQ4hJp8euc

[William Bezuidenhout @BurmudarFTL]

@pjlast_ You could always attempt https://t.co/ag8mS5sdxV and then post your failure to Linkedin and how you grew your b2b sales because of it

[William Bezuidenhout @BurmudarFTL]

@pjlast_ And they were so fast that they had to make fillers so that the manga could catch up.

[Thorsten Ball @thorstenball]

Full news post with more links is here: https://t.co/oIC7wzJHZa

Thank you to @michael_bahr_sg, @pjlast_, and @burmudarFTL for building this.

And thanks to @fatih for providing very valuable early feedback and testing it!

[Beyang @beyang]

Cody now has a mechanism for pulling in context from *outside* the codebase!

Introducing OpenCtx, a protocol for providing relevant technical context to humans and AI. This builds on Sourcegraph's foundation as the world's best code search and connects our code graph to entities like issues, designs, technical docs, production logs, how UI components are rendered, and beyond.

As AI advances, we think it's important to have an open specification of how context is provided and integrated. Think of this as an "LSP for technical context" that makes it possible to integrate data from many tools across a diverse set of vendors. It will make it much easier to surface relevant context wherever you need it to accelerate software development—while preserving the freedom to choose the best tool at every point in the software development lifecycle.

If you've ever wished you could jump immediately from a line of code to (a) the production logs that hit that line, (b) a rendering of the UI component implemented by it, (c) the PRs that touched it, (d) the design docs that mentioned it, (e) whatever other discussion or documentation is relevant in some way, then you've dreamed of the future that OpenCtx is seeking to realize.

We currently use OpenCtx in two ways at Sourcegraph: (1) as a experimental context provider for Cody, for context-aware AI code generation and (2) as annotations within source files that tie symbols in the code to the relevant technical context that lies outside of source code. We think (2) is as important as (1), because we believe human developers will remain the heart and soul of the software development process.

We will build *much* more on top of this protocol and look forward to building with our community to integrate many other tools into it, as well!

[Sourcegraph @Sourcegraph]

It can be annoying to switch between tools when coding: open the issue in @linear or @Jira, jump into @figma, look up the error on @getsentry, and so on.

With OpenCtx, an open standard for bringing info from all these tools into anywhere you read code, you don't have to.

[William Bezuidenhout @BurmudarFTL]

@ipmb @simonw A bit biased but https://t.co/NzK9OQvj7x

[Quinn Slack @sqs]

Our team ships fast! GPT-4o shipped in Cody just after it was announced.

[ollama @ollama]

Llama 3 can now be used in @SourcegraphCody to chat with your code!

Check it out 👇👇

[Beyang @beyang]

PSA for security researchers investigating the xz exploit: GitHub disabled the repository, but you can still explore the source on Sourcegraph. Diff search might be useful for finding/grokking contributions Jia Tan made to other projects (like google/oss-fuzz), as well:

[William Bezuidenhout @BurmudarFTL]

@pjlast_ Me being sick from travel: travel is the audacity of man defying nature and has been a mistake since we moved from sea to land

[Quinn Slack @sqs]

this is your weekly reminder that cody is open source: https://t.co/a0fpLFiFJI

[Cesar Jimenez @cesar_r_jimenez]

In this quick 1min video, I try to trick Cody and succeed! 😈

But by giving him Sourcegraph SCIP data, he’s not so easily fooled 😓

Check it out!

P.S. You can try Cody yourself.

It’s free. 😉

👉 https://t.co/lHi4dC34vP

[Sourcegraph @Sourcegraph]

Moving past 1st-generation coding copilots that use only open tabs for context, Cody now looks up relevant code from your broader codebase. This reduces hallucinations and generates code that better "fits" into your existing code. It's also free ;) https://t.co/1NDR5HEk7X

[(Dr.) Eric Fritz @ericfritz]

@sourcegraph @SourcegraphCody :letsgooooooo:

[Sourcegraph @Sourcegraph]

Software Engineer, ⭐️Prompt Engineer⭐️ or 🌟AI Engineer🌟—no matter what you are, good ol' fashioned dev tools are still crucial to your productivity.

Cody takes us on a tour of telescope.nvim with its creator @teej_dv—and guess which editor Cody is coming to soon? ;)

[Sourcegraph @Sourcegraph]

Cody for Sourcegraph 5.1 is here, bringing AI to every part of your coding workflow.

More contextually-aware, available wherever you write code. https://t.co/n3HRkwCW1D

[William Bezuidenhout @BurmudarFTL]

@pjlast_ Some sins cannot be forgiven in the church of vim

[Sourcegraph @Sourcegraph]

Ever wonder how Sourcegraph uses Cody? One of our engineers' shares:

"[...] I’m writing up the description for the PR, and I’m struggling to describe the current situation, so I turn to Cody for help.
With a minimum of input (I didn’t have to craft a long and precise question), Cody concisely and accurately sums up the situation, leaving me, well, rather speechless."