beyang (u/beyang) - Readit News

beyang commented on My experience with Claude Code after two weeks of adventures sankalp.bearblog.dev/my-c... · Posted by u/dejavucoder

Wowfunhappy · a month ago

> Personally, I also like that usually it just presents to me only one change/file at a time, so it's easier for me to review

This is interesting. I haven't used Cursor, but one of my frustrations with Claude Code is that some of the individual changes it asks me to approve are too small for me to make a decision. There are cases where I almost denied a change initially, then realized Claude's approach made sense once I saw the full change set. Conversely, there are cases where I definitely should have stopped Claude earlier.

It doesn't help that Claude usually describes its changes after it has made the full series, instead of before.

...really, what I'd like is an easy way to go back in time, wherein going back to an earlier point in the conversation also reverted the state of the code. I can and do simulate this with git to some extent, but I'd prefer it as a layer on top of git. I want to use git to track other things.

beyang · a month ago

If you like Claude Code but either (1) prefer an agent that doesn't ask for review on each file edit or (2) miss the IDE for things like reviewing diffs, I'd humbly submit you try out Amp: https://ampcode.com. It has both a CLI and VS Code extension, and we built it from the ground up for agentic coding, so no asking for permission on each edit, a first-class editor extension (personally I spend more and more time reviewing diffs and VS Code's diff view is great), and it employs subagents for codebase search and extended thinking (using a combo of Sonnet and o3) to maximize use of the context window.

beyang commented on GitHub Copilot is now available for free github.com/features/copil... · Posted by u/ksec

JadoJodo · 8 months ago

Has anyone who uses an IDE (e.g., JetBrains, not a code editor) moved to Cursor? I've downloaded it a few times because everyone raves about it, but I've always come back almost immediately because editors can't reliably make changes across projects (among many other things)... What am I missing?

FWIW I use GoLand w/ Supermaven, currently.

beyang · 8 months ago

Check out Cody for GoLand and JetBrains: https://plugins.jetbrains.com/plugin/9682-cody-ai-coding-ass...

beyang commented on GitHub Copilot is now available for free github.com/features/copil... · Posted by u/ksec

beyang · 8 months ago

For those looking for a free coding assistant they can also use at work / in the enterprise, Cody has had a free tier for awhile: https://sourcegraph.com/cody

- Works with local models

- Context-aware chat with very nice ergonomics (we see consistently more chats per day than other coding assistants)

- Used by both indie devs and devs at very large enterprises like Palo Alto Networks

- Hooks nicely into code search, which is important for building a strong mental model inside large, messy codebases

- Open source core

beyang commented on GitHub Copilot is now available for free github.com/features/copil... · Posted by u/ksec

verdverm · 8 months ago

I'd prefer something where I can bring my own model and pay the API costs directly, rather than yet another $20+/m/dev fee

The free plan is not going to work for professional coding

beyang · 8 months ago

FYI, you can do that with Cody + Ollama. A good portion of our user community does exactly that: https://sourcegraph.com/blog/local-code-completion-with-olla...

beyang commented on AI Stole the Joy of Programming paulefou.com/blog/ai-cuck... · Posted by u/svalee

dsissitka · 9 months ago

It's frustrating.

Cody's autocomplete used to work really well for me. Then they switched to DeepSeek. Now I regularly get suggestions that are irrelevant, incomplete, and contain syntax errors.

I'm not sure what it's like these days but I had a similar experience with Copilot a while back.

I wonder if good autocomplete is just too expensive.

beyang · 9 months ago

Hi there, Cody contributor here—sorry to hear you had a bad experience! In our evals, our DeepSeek variant outperformed previous models and other alternatives. If it's working worse for you know, would be open to sending us some examples/screenshots of poor completions examples? We'd like to incorporate these into our eval set so we can capture a more representative distribution of codebases and how Cody performs!

beyang commented on Sourcegraph went dark eric-fritz.com/articles/s... · Posted by u/kaycebasques

depr · a year ago

I hope code search will one day be offered at a lower price, so small/medium sized companies can use the product. I'll never be able to convince someone to buy it when it's 3 or more time as expensive source code hosting, and would in many cases be most expensive SaaS product per developer seat that the company uses. But it's a great product.

beyang · a year ago

This is in the cards and thank you for the feedback! (Sourcegraph CTO here)

beyang commented on An ex-Googler's guide to dev tools (2020) sourcegraph.com/blog/ex-g... · Posted by u/intrepidsoldier

beyang · 2 years ago

Author of the post here—as another commenter mentioned, this is indeed a bit dated now, someone should probably write an updated post!

There's been a ton of evolution in dev tools in the past 3 years with some old workhorses retiring (RIP Phabricator) and new ones (like Graphite, which is awesome) emerging... and of course AI-AI-AI. LLMs have created some great new tools for the developer inner loop—that's probably the most glaring omission here. If I were to include that category today, it would mention tools like ChatGPT, GH Copilot, Cursor, and our own Sourcegraph Cody (https://cody.dev). I'm told that Google has internal AI dev tools now that generate more code than humans.

Excited to see what changes the next 3 years bring—the pace of innovation is only accelerating!

beyang commented on GitHub: Can no longer search code without being logged in github.com/orgs/community... · Posted by u/6581

beyang · 2 years ago

If folks want to continue searching open source, https://sourcegraph.com/search does not require sign in and also includes major projects that are not on GitHub.

(Full disclosure: I'm the Sourcegraph CTO)

beyang commented on Code Search at Google: Han-Wen and Zoekt sourcegraph.com/blog/zoek... · Posted by u/intrepidsoldier

frutiger · 2 years ago

I’m a bit confused as to how https://swtch.com/~rsc/regexp/regexp4.html isn’t mentioned at all.

beyang · 2 years ago

Zoekt was heavily inspired by Google's internal code search, as mentioned in the blog post. The original version of the internal code search is described in the rsc post. Zoekt keeps some of the foundational ideas (e.g., trigram index), but was a from-scratch implementation. We probably should link to the rsc post for completeness, will update.

beyang commented on Code Search at Google: Han-Wen and Zoekt sourcegraph.com/blog/zoek... · Posted by u/intrepidsoldier

j2kun · 2 years ago

IIUC, the main thing that Google's internal codesearch does that makes it superior to external systems (outside of an IDE, like GitHub code search) is that Google actually builds everything, and so it can incorporate that information into its index. There's only so much text search can do when you have macros generating code.

beyang · 2 years ago

Great call out! We've built this code navigation infra on top of Zoekt into Sourcegraph. Example: https://sourcegraph.com/github.com/golang/go/-/blob/src/net/...

Docs: https://docs.sourcegraph.com/code_navigation/explanations/pr...