Y
HN Search
Hacker News Search
new
|
comments
|
top
|
jobs
beliu
searching Neon…
1.
▲
2.
▲
3.
▲
4.
▲
5.
▲
6.
▲
13 ms
·
1.
▲
Throwaway Development Environments with Nix
(monospacedmonologues.com)
2 points
by
beliu
4y ago
|
0 comments
2.
▲
by
beliu
4y ago
In case folks are interested, I had a delightful interview about a year back with Max Brunsfeld, one of the original Atom devs who is now working on Zed: https://about.sourcegraph.com/podcast/max-brunsfeld . (YouTube li
3.
▲
by
beliu
4y ago
LOL! He did talk a lot about his programming backstory (played with BASIC as a kid, no formal training, chemistry major, discovering Linux) and how this informed his worldview. Bottom-line, he is very results-driven and I think he has a g
4.
▲
by
beliu
4y ago
This is super common in my experience. Senior/experienced devs spend a bunch of time ramping up the inexperienced or new members of the team and don't have much time remaining to work on their own initiatives. Patrick McKenzie has
5.
▲
by
beliu
4y ago
Thanks! 100% agree with the sentiment that devs should get in front of customers. The best teams I've worked on, the devs have an "end-to-end" sense of ownership, and the organization fosters this sense of responsibility and
6.
▲
by
beliu
4y ago
World's best code search: https://sourcegraph.com/search Analyze code as data: https://sourcegraph.com/insights Interactive docs you'll actually use: https://sourcegraph.com/notebo
7.
▲
by
beliu
4y ago
This is really important to call out. There have been a lot of really bad practices in the past that try to reduce "developer productivity" to something that approximates a widget factory, and the results have been awful for both
8.
▲
by
beliu
4y ago
Sourcegraph actually does do proper semantic linking, integrating with compilers (and type inferencers for dynamic languages): https://docs.sourcegraph.com/code_intelligence/explanations/... . This is one area of s
9.
▲
Key elements of successful monolith-to-microservices migrations
(about.sourcegraph.com)
2 points
by
beliu
4y ago
|
0 comments
10.
▲
by
beliu
4y ago
I’m helping with the doctree effort at Sourcegraph. Apologies, the site isn’t actually up yet. This project is still very early stages and we wrote up the README to serve as a sort of launch spec that we could update in response to feedback
11.
▲
by
beliu
4y ago
Sourcegraph CTO here. Does anyone know someone at GitHub or Microsoft we could get in touch with to take over maintenance of git.io? There are hundreds of thousands of references in open source, blog posts, and academic papers that will 404
12.
▲
by
beliu
4y ago
Here is a list of open source projects that should update their git.io URLs, ranked in order of popularity: https://sourcegraph.com/search?q=context:global+https://git....
13.
▲
CVE-2022-21449: easily exploitable unauthorized read/write to critical data
(access.redhat.com)
2 points
by
beliu
4y ago
|
0 comments
14.
▲
by
beliu
4y ago
Actually that’s not quite right. We offer auto-indexing now for some languages with more on the way. If neither auto-indexing nor manual LSIF generation are an option, we fall back to our search-based code navigation, which, similar to GitH
15.
▲
by
beliu
5y ago
This reminds me of Shaple: https://swag.github.io/shaple
16.
▲
by
beliu
5y ago
Thank you for this super clear and concise write-up. Used it to write up these instructions for our users and customers to patch the vulnerability across their codebase and sharing here in case it's of use/interest to others: htt
17.
▲
by
beliu
5y ago
Appreciate the feedback here (Sourcegraph CTO). I agree that's annoying. Kicking off a conversation on our end to figure out how to fix that. In the meantime, the workaround would be to create a separate GH login, which can be used to
18.
▲
by
beliu
5y ago
Hey Edwin, if you're open to providing feedback, I'd love to understand which types of searches worked well for you in Google Code Search but not in Sourcegraph. We've invested a lot of thought into our query syntax, supporti
19.
▲
by
beliu
5y ago
Sourcegraph is open-core, with a dual licensing approach. You can run the open-source version here: https://github.com/sourcegraph/sourcegraph#sourcegraph-oss , and we have an enterprise offering for companies that want
20.
▲
by
beliu
5y ago
We built Sourcegraph taking inspiration from Google Code Search ( https://about.sourcegraph.com/blog/ex-googler-guide-dev-tool... ) to bring the power of code search—and precise code intelligence that just works—to every
21.
▲
by
beliu
5y ago
Sourcegraph CTO here, I'm very sorry this happened with you. If you shoot me your email (I'm reachable at beyang@sourcegraph.com), I'll ensure you don't receive any future sales/marketing emails from us. This is som
22.
▲
by
beliu
5y ago
Sourcegraph CTO here, thanks for posting this feedback. Yes, we do collect information from self-hosted instances of Sourcegraph. (Note to other readers: the blog post is talking about sourcegraph.com whereas what we are discussing here is
23.
▲
by
beliu
5y ago
Hey, I'm the CTO/co-founder of Sourcegraph. Thanks for the feedback here. I've opened up a pull request to make it clearer how to disable non-critical telemetry: https://github.com/sourcegraph/sourcegraph
24.
▲
by
beliu
5y ago
Sourcegraph | Full-time Eng, Product, Design | REMOTE | https://sourcegraph.com We're building the Google for Code and making great code search (the kind that Google, Facebook, and Microsoft have internally) accessible to e
25.
▲
Linux Privilege Escalation – Exploiting Capabilities
(steflan-security.com)
2 points
by
beliu
5y ago
|
0 comments
26.
▲
Screenshots from Developers: 2002 vs. 2015
(anders.unix.se)
57 points
by
beliu
6y ago
|
9 comments
27.
▲
by
beliu
6y ago
Author of the post here. I would say that technically Kythe is the open-source version of part of Google's internal code search (specifically, the component that provides precise code navigation), but it doesn't include the sear
28.
▲
by
beliu
6y ago
Author of the post here. We're actively working on this at Sourcegraph. Up until recently, we've focused on working well on large private codebases, but looking forward, we have two big efforts that will make this a reality on sou
29.
▲
LostInTangent on Building Codespaces, Live Share, and CodeTour (transcript)
(about.sourcegraph.com)
1 points
by
beliu
6y ago
|
0 comments
30.
▲
BurntSushi talks about creating ripgrep (audio and transcript)
(about.sourcegraph.com)
4 points
by
beliu
6y ago
|
0 comments
More ›