Stanford Seminar - Google's Steve Yegge on GROK
Stanford Online3 HN recommenders · recommended in 4 months, 2013-2024
30K views · 14 years ago · talk · evergreen
Steve Yegge's Stanford seminar on GROK, Google's internal large-scale, cross-language source code analysis system. It covers how the system helps with code search and understanding across Google's huge codebase.
HN refers to it as the main public description of Google's internal code analysis tooling, and as a precursor of ideas like LSP.
45:11Stevey's Tech Talk E39 -- A guided tour of Emacs
Steve Yegge
13K views • 4 years ago
15:05Steve Yegge, "What Would You Do With Your Own Google?" - OSCON Data 2011
O'Reilly
66K views • 15 years ago
1:22:45Building Software Systems At Google and Lessons Learned
Stanford
257K views • 15 years ago
52:21ASPLOS Keynote: The Golden Age of Compiler Design in an Era of HW/SW Co-design by Dr. Chris Lattner
SiFive
52K views • 5 years ago
25:17Interview with Steve Yegge on Rhino on Rails and more
Google for Developers
34K views • 18 years ago
17:26Lecture 1 | Programming Paradigms (Stanford)
Stanford
1.2M views • 18 years ago
1:01:37Compiling and Optimizing Scripting Languages
Google TechTalks
21K views • 17 years ago
1:10:11Self and Self: Whys and Wherefores
Stanford
30K views • 16 years ago
56:39Alan Kay - Programming and Scaling
Colin McDonnell
36K views • 11 years ago
40:56"Liberating the Smalltalk lurking in C and Unix" by Stephen Kell
Strange Loop Conference
25K views • 12 years ago
1:26:02Stanford Seminar - The Soul of a New Machine: Rethinking the Computer
Stanford Online
76K views • 6 years ago
1:38:36Episode 1: A basic expression evaluator
Immo Landwerth (terrajobst)
284K views • 8 years ago
1:00:29Google I/O 2012 - Meet the Go Team
Google for Developers
108K views • 14 years ago
1:04:45Stanford Seminar - Concatenative Programming: From Ivory to Metal
Stanford Online
14K views • 8 years ago
49:47Lecture 1 | Programming Methodology (Stanford)
Stanford
2.6M views • 18 years ago
38:38"Tree-sitter - a new parsing system for programming tools" by Max Brunsfeld
Strange Loop Conference
63K views • 8 years ago
39:49Hammock Driven Development - Rich Hickey
ClojureTV
333K views • 13 years ago
30:50Why Google Stores Billions of Lines of Code in a Single Repository
@Scale
317K views • 11 years ago
24:02How to: Work at Google — Example Coding/Engineering Interview
Life at Google
7.6M views • 10 years ago
2:42:41Chris Lattner: The Future of Computing and Programming Languages | Lex Fridman Podcast #131
Lex Fridman
594K views • 6 years ago
11 comments from Hacker News
LSP is basically an open(-ish) source implementation of Google’s internal tool called Grok. Grok was made by Steve Yegge, a formerly famous tech blogger. Steve Yegge uses emacs, and half his motivation was to equalise editors by moving the language processing elements to an external place that’s shareable by all. He has a great talk on it: ▶ this video . So it’s, like, not an accident that emacs can leverage this :-D. Though I never see anyone giving him credit.
Steve Yegge talking about the system he built at Google, called Grok: ▶ this video . If we have anything half that good in the wider programming community in twenty years time, I will be very surprised.
Yes, and they've open sourced part of that here (at least, I think it is related, and is also called "Code Search"): link But, their public code search was not the same as the internal thing, as far as I know. The internal beast sounds kind of awesome. Here's his talk about it from a few years ago: ▶ this video I think the really useful thing (beyond a mere search engine that has indexed a lot of source code) is the comprehension of the "guzzintas" and "guzzouttas" of the code, more than merely a naive word search; i.e. knowing how pieces interact, so you can search for functions that work with a particular kind of object, for example, or objects that have the same properties, or code that interacts with the same API you're working with, whatever.
Steve Yegge has spoken about the search tool his team built to solve the "has someone else written this?" and "refactor this" for all the languages and systems across Google. ▶ this video
For those interested, the source analyzer Steve Yegge was working on called GROK has been renamed Kythe. I don't know how useful it turned out to be for those 2B LOC. link Steve Yegge, from Google, talks about the GROK Project - Large-Scale, Cross-Language source analysis. [2012] ▶ this video
This looks very nice; automated access to and analysis of the huge amounts of source code on the Internet could be a game changer for programmers everywhere. As an aside, when I saw Google in the URL I thought that this was a rebranding of Steve Yegge's "Grok"[0] project. Does anyone know what's happened to that? [0] ▶ this video
This looks very much in the spirit of Yegges' 'Grok' project at Google [1][2]. Does anyone know if that project is still alive? [1] link [2] ▶ this video
He actually has been working on a big data analysis problem for the last four years, which is presumably why he was asked to speak, so your characterization of him as all talk and no action is incorrect ▶ this video
Steve Yegge at Google is/was involved in a project called 'Grok' which sounds pretty similar to that. I really hope it catches on also. link ▶ this video HN discussion: link
As another year ex-Googler, I'd say this is BS. Everything that superseded the "gconfig" days was pretty amazing, and IIRC the team behind it in NY did quite well for themselves. Steve Yegge wrote GROK, which is an internal tool, and I'm pretty sure no one around here looks down on him: ▶ this video
I wouldn't want to use the term "best" because there are so many good ones in various areas, but this talk by Steve Yegge was both entertaining and informative. Stanford Seminar - Google's Steve Yegge on GROK (large scale source code analysis) ▶ this video