782 karma · joined September 25, 2011
And yes, congratulations to the Neon team! (Nikita is, after all, YC)
Second — it’s amazing the detail that you can achieve from public data.
Third — I’m left wondering if a true “Deep Research” like tool would be able to provide the same analysis. I find that Deep Research is fine for secondary sources, but not for Deep Analysis of primary source data.
The hackathons I remember as a college student were different. They were much more free form. You were asked to create something around a broad topic: eg graphics, operating systems, modeling a neuron. You were allowed and encouraged to go outside the box.
Getting the prize was fun, but a working artifact was much more satisfying. That’s why we did it.
So, yes, it’s too commercial these days.
While I don't like VC math and we (I'm CEO and co-founder) at Aryn AI give more than 1% for founding engineers, numbers like 5% to 25% are really a reflection of the risk and not the work. Prior to an equity round, you can give that away and you're treating the founding engineers like minor founders. Post an equity round, there isn't enough left to give everyone that and still build a decent team.
After an equity round with decent funding for 2-3 years, the co-founders have convinced someone to part with lots of money with no guarantee of an exit. There are innumerable YC startups and well-known VC-backed companies that have been sold for parts. After an equity round, you are joining a startup with some runway that you would not have gotten on your own, and hopefully, working on an opportunity that is outsized. Otherwise, you shouldn't take it.
Outsized means that even if the founders are gazillionaires, you may be 1/20 of a gazillionaire, which is still a gazillionaire. Otherwise, it would have been better for everyone to have worked for some big tech firm anyways. It really is a zero to one game, and you don't get to do it often. So do it if its compelling and fun and the outsized reward is and has always been a lottery ticket.
Nice post and response to the previous one.
It’s important to remember that the use cases for VLMs and document parsers are often different. VLMs definitely take a different approach than layout detection and OCR. They’re not mutually exclusive. VLMs are adaptable with prompting, eg please pull out the entries related to CapEx and summarize the contributions. Layout parsers and OCR are often used for indexing and document automation. Each will have their own place in an enterprise stack.
Good post. VLM models are improving and Gemini 2.0 definitely changes the doc prep and ingestion pipeline across the board.
What we're finding as we work with enterprise customers:
1. Attribution is super important, and VLMs are there yet. Combining them with layout analysis makes for a winning combo.
2. VLMs are great at prompt-based extraction, but if you have document automation and you don't know where in tables you'll be searching or need to reproduce faithfully -- then precise table extraction is important.
3. VLMs will continue to get better, but the price points are a result of economies of scale that document parsing vendors don't get. On the flip side, document parsing vendors have deployment models that Gemini can't reach.
Scaling this model is hard, however, and I think they may be running into scaling limits. There just may not be that many fast growing businesses (startups) every year. We won't know until years from now.
Examples on non-monotonic computation (i.e. that don't fit) include aggregations, in particular those that include time series with windows. The answer depends on what is in the window. So, if you take an average and only include a subset of the data in a window, the output will change when you add more data in the window. At least, that's how I interpret the monotonic requirement.
I couldn’t have said it better. This is why I’m an entrepreneur and still take the pains to do it.