wasimlorgat

7 ms·

1.
Building a cost-effective image vector search engine with CLIP(wasimlorgat.com)
2 points by wasimlorgat 3y ago|0 comments
2.
Jupyter Server: A Whirlwind Tour(wasimlorgat.com)
2 points by wasimlorgat 4y ago|0 comments
3.
by wasimlorgat 4y ago
Very cool how you pieced together these OS libraries and models! TIL about PythonAnywhere. Would it be possible to have your task/script update the index.html file? Since that’s the only thing that updates the feed, it might be a nice
4.
by wasimlorgat 4y ago
Thanks for sharing! Hmm, it isn’t clear to me from your post why a library would be harder to maintain. Could you share more? The database seems to add quite a bit of complexity at a system-level and I’m still not sure the benefit.
5.
by wasimlorgat 4y ago
Qdrant looks great, thanks for sharing! I'll definitely play around with it and do some benchmarks :) Have you used it / compared it with faiss yourself?
6.
Show HN: I built an AI-powered search engine for a fashion and homeware store(meepo.shop)
5 points by wasimlorgat 4y ago|6 comments
7.
From Deep Learning Foundations to Stable Diffusion(fast.ai)
258 points by wasimlorgat 4y ago|34 comments
8.
by wasimlorgat 4y ago
I'm always surprised when people advocate for .py files over notebooks because of poor software practice. (Genuine question) have you found that it improves the situation at all?
9.
by wasimlorgat 4y ago
Oh, on the topic of file formats: Quarto also lets you do plaintext notebooks in quite an interesting way, definitely worth checking out: https://quarto.org/docs/computations/python.html
10.
by wasimlorgat 4y ago
Have you worked with Jupyter notebooks and git? It's a literally true statement :D and quite a struggle for many of us
11.
by wasimlorgat 4y ago
It does an ordinary three-way git merge (treating notebooks as plaintext) then a two-way merge on conflicted bits. We opted for that approach because its incredibly simple and has worked perfectly for us (I think since we tend to work with
12.
by wasimlorgat 4y ago
I agree re format vs tool complexity. I don't think Jupyter is a particularly difficult format though, its mostly light JSON -- all human-readable. We realised after working with Jupyter+Git for a while that the pain-points were actual
13.
by wasimlorgat 4y ago
Jupytext does a lot more than just fix Jupyter/git integration, which is great if you want to adopt its approach, but a bit too heavy IMO if you don't. The approach mentioned here is extremely lightweight and doesn't use too
14.
by wasimlorgat 4y ago
Hi, I'm the author of the git merge driver and Jupyter save hook in nbdev2 :) I'd be happy to answer any questions you have about how we're handling using notebooks with git