There’s a lot to unpack in the quoted passage, but it is not an ad hominem attack. That you think it is, and then turn around to make an ad hominem argument of your own explains your misinterpretation.
If anything this will turn out to be the opposite of the truth: People hit by autonomous cars will have more to go after in court than those hit by individuals, many of whom don't have adequate coverage or savings to compensate victims. The minimum "bodily harm" insurance coverage in California is only $15,000.
He talks about the courage it takes to do risky work in our field, and gives practical techniques for overcoming barriers, such as having collaborators, deadlines, "just get started", stock compensation, etc.
Dr Sutherland also discusses the courage to keep going, or even _stop_ working on a project.
Given his broad background, he discusses how these dynamics play out in a wide range of fields, including education, startups, and research.
It could be doing some "fine tuning" based on the repo. That would be cool! That said, what I meant when referring to 'understanding' the non-local nature of code was in a more principled way.
For example, if an object defined in another file has a function called `rename` that takes zero arguments, when calling it from another file Copilot will likely suggest arguments if there are variables like `old` and `new` near the cursor, even though `rename` actually doesn't take any, just because functions called `rename` typically take arguments. This behavior is in contrast to a tool like an IDE that can trace through the way non-local code references work.
Does it seem to only understand imports of public libraries? If so, it's likely that, rather than understanding the contents of those libraries, it's learning from others' use of those library APIs. If not, it is likely just understanding the words in the API at a shallow depth.
Yes, this was precisely what I was referring to. In small-enough programs (e.g. one file) Copilot has all the context. The other extreme would be something like the Chromium codebase. Because of this, Copilot looks better in quick demos than real-world use. (Though of course it is very impressive and this tech will get there, hopefully very soon!)
I suspect they will dominate all the largest technology markets for the long run, unless the government intervenes. I might be wrong.
They may not dominate the future of "technology markets", though, if the sum of the long tail dominates. Right now FAANG is 42% of the NASDAQ Composite 100.
> I've tried to explain this to VC firms. Instead of making one $2 million investment, make five $400k investments. Would that mean sitting on too many boards? Don't sit on their boards. Would that mean too much due diligence? Do less. If you're investing at a tenth the valuation, you only have to be a tenth as sure.
This turned out to be absolutely right, and the < $2M checks have ballooned in volume. They are invested by firms that do not take board seats and do comparatively less due diligence.
That said with the benefit of more hindsight I think the reason there are no more Googles is that FAANG has a stronghold on the largest technology markets.
The turnarounds always happen quickly after the fed takes serious action. Consider the 2008 crisis, or take 1933 (I believe?) when we broke from the gold standard: immediate exit from the Great Depression.
The fed and congress have been very on point with the stimulus response speed this time around and so I think we’ve seen the bottom of the market through this. And most investors are voting with their dollars that this is true.
We hope you'll give Kite another shot. We're always improving it and have covered a lot of ground in the last few years.
In particular, a common complaint about TabNine on Twitter is that it's heavyweight. Based on our comparisons of today's Kite versus today's TabNine, we believe Kite uses less CPU/battery, and far less memory. (My teammate dhung posted a longer comment about TabNine.)
We hear you. We agree this was a mistake, and over the ~three years since then we've listened to the community, for example by releasing local processing for Kite.