HackerTrans
トップ新着トレンドコメント過去質問紹介求人

bothra90

no profile record

投稿

How we built a vector search engine in 200 lines of Rust

fennel.ai
2 ポイント·投稿者 bothra90·3 年前·0 コメント

Micromanagement (sometimes) good?

lethain.com
2 ポイント·投稿者 bothra90·3 年前·0 コメント

The case for consolidation

benn.substack.com
39 ポイント·投稿者 bothra90·4 年前·11 コメント

ML behind recommendation systems at FAANG

blog.fennel.ai
5 ポイント·投稿者 bothra90·4 年前·0 コメント

The Case for Consolidation

benn.substack.com
3 ポイント·投稿者 bothra90·4 年前·0 コメント

Sibyl – Prediction Service at DoorDash (2020)

doordash.engineering
27 ポイント·投稿者 bothra90·4 年前·36 コメント

Big Data Serving – The Hardest Problem in Computing

medium.com
1 ポイント·投稿者 bothra90·5 年前·0 コメント

Sibyl – Prediction Service at DoorDash

doordash.engineering
3 ポイント·投稿者 bothra90·5 年前·1 コメント

Merlion – A new time-series ML framework from Salesforce

github.com
7 ポイント·投稿者 bothra90·5 年前·0 コメント

The Rise of Worse Is Better – Richard P. Gabriel (1991)

dreamsongs.com
2 ポイント·投稿者 bothra90·5 年前·0 コメント

Dislike for Pull Requests

draconianoverlord.com
1 ポイント·投稿者 bothra90·5 年前·1 コメント

コメント

bothra90
·2 年前·議論
Is this competing with Nessie (https://projectnessie.org/)?
bothra90
·3 年前·議論
That would be awesome!
bothra90
·3 年前·議論
Exciting work! Some questions:

1. Any plans on open-sourcing this?

2. Why not have a tiered architecture that can provide lower latency? p99 of 1s can be too high for some use-cases.

3. Related to 2, how does WarpStream compare to tiered storage in Pulsar?

[Edit 1] Added (3)
bothra90
·4 年前·議論
Can you share some insight on how/if Kagi is different from Neeva[1] in its approach?

[1] https://neeva.com/
bothra90
·5 年前·議論
By an independent board do you mean that the H1B holder cannot themselves be on the company's board? Re: 50% ownership, is 50-50 split OK, or does it have to be less than 50?
bothra90
·5 年前·議論
Is this solving similar problems as Ray [1]?

[1] https://www.ray.io/
bothra90
·5 年前·議論
How does this compare with https://github.com/linkedin/greykite?
bothra90
·5 年前·議論
I really wish more design docs / project reports looked like this article - talking about the whys, goals / non-goals, options considered, prototypes built, challenges, and solutions, learnings and next steps. Kudos!
bothra90
·5 年前·議論
Although GitHub supports the commit-based review the author is arguing for (they found it too after writing the article), I don't think it completely solves the problem - we need to be able review, test, and merge each commit individually without needing to merge the entire PR. Since GitHub doesn't have first-class support for dependent PRs, we are still "stuck" with a broken workflow. An example workaround: https://wchargin.github.io/posts/managing-dependent-pull-req.... Are there any better solutions?