Steve Yegge Joins as Head of Engineering of Sourcegraph

The length of the article is how you know it&#x27;s the real Steve Yegge. :)<p>Youngbloods: if you have not spent time with Steve Yegge&#x27;s old writings, please go check them out. Much good received wisdom there.

Sourcegraph CTO here. We&#x27;re elated to welcome Steve to the team and will be hosting a Twitter live &#x2F; AMA (<a href="https:&#x2F;&#x2F;twitter.com&#x2F;sourcegraph&#x2F;status&#x2F;1577364344056201236" rel="nofollow">https:&#x2F;&#x2F;twitter.com&#x2F;sourcegraph&#x2F;status&#x2F;1577364344056201236</a>) with him tomorrow at 1pm PT. Join us if you&#x27;re free!

I see the Steve Yegge cycle begins anew.<p>1 Join a company<p>2 write a lengthy, self-important diatribe&#x2F;novella about why he joined<p>3 Write several lengthy, self-important diatribes, often namedropping previous places he worked and&#x2F;or how he accidentally influenced some C level officer just by dint of his unique persona =) That rascally Steve!<p>4 Repeat step 3 anywhere between 10-50 times<p>5 Quit job, write lengthy self-important diatribe about why he left (optionally leaping straight into step 1 again, sometimes with a break inbetween)<p>Should be an interesting 6 months for Sourcegraph, at least! Looking forward to seeing how this progresses.

I can&#x27;t help but read Steve Yegge&#x27;s announcement in the context of Novig&#x27;s Law (&quot;compiler research leads to a doubling of compute power every 18 years&quot;)[0].<p>If his presence and enthusiasm can get the compiler community aiming its collective brain power at real developer productivity problems (the why behind SourceGraph&#x27;s exponential growth) rather than focused on compiler optimization problems, this is going to be a really great time to be writing software!<p>[0] <a href="https:&#x2F;&#x2F;norvig.com&#x2F;norvigs-law.html" rel="nofollow">https:&#x2F;&#x2F;norvig.com&#x2F;norvigs-law.html</a>

How does sourcegraph compare to the new&#x2F;beta <a href="https:&#x2F;&#x2F;cs.github.com" rel="nofollow">https:&#x2F;&#x2F;cs.github.com</a>?

I really like the idea of sourcegraph but the price seems bonkers. $100&#x2F;month&#x2F;user is more than I spend on ides, more than GitHub, the same as GitLab ultimate (that I don’t use because it’s so expensive), more than o365, more than windows, etc etc etc.<p>I want to have source intelligence but I can’t see the biggest chunk of my dev stack to be sourcegraph.

Article raises 2 questions for me.<p>1) How can you write this whole article without saying &quot;Kythe&quot;?<p>2) How exactly can github search be as bad as it is? With all of Microsoft behind it, you&#x27;d think it would be a lot better than it is.

&quot;This was the first leadership interview loop in the past 12 months (20+ companies) in which anyone had asked me to write code.&quot;<p>Interesting data point for the question: at what point in your career will you stop being asked to write code on a whiteboard to prove you aren&#x27;t lying on your resume.

I&#x27;m really curious to see how this plays out. My ex-roomate has a very bad experience working at sourcegraph and the way he was pushed out of the company left a bad taste in my mouth. I&#x27;m curious to see if Steve&#x27;s brand is strong enough that he&#x27;ll have the power to be able to improve the engineering culture, my fear is that this is a hire primarily for external optics reasons.<p>Anyway, just sharing an anecdote and hope this works out well for all involved.

Weren’t they just laying off a bunch of people? Now on a hiring spree?

I&#x27;ve watched that Grok video a dozen times and drooled at the possibilities if it were available to the world at large. And now it is!! It&#x27;ll also be nice that people will remember that Grok came long before LSP :P

&gt; But you don’t have to join Sourcegraph to be able to party with us. Our code and our development are public<p>Oh cool - AFAICT, that &quot;our code&quot; link is a link to a demo instance of sourcegraph on sourcegraph&#x27;s code. This looks like an interesting product.<p>And it&#x27;s open source? What&#x27;s present in the commercial offering that&#x27;s missing from the open source one? Just support, or features too?

When I investigated sg for former gig I found out that bazel was still not supported. How does uber uses it for their monorepo in that case?

What a nice read again - haven&#x27;t had these in a while. I wonder what Mr. Yegge&#x27;s position on the best language is nowadays.

Someone help me understand what I&#x27;m missing. It sounds like in this article Steve Yegge is describing a tool like Atlassian Fisheye or grepcode and talking about it like it doesn&#x27;t exist. These tools are out there. I don&#x27;t see what&#x27;s missing.

Who is Steve yegge?

I haven&#x27;t finished the article yet but someone please clarify to me: I thought &quot;Language Server Protocol&quot; had solved this?