j0selit0

8 ms·

1.
I don't need 100s of Codex agents(lighthousenewsletter.com)
2 points by j0selit0 7d ago|1 comments
2.
by j0selit0 7d ago
I need changes I can understand and review
3.
by j0selit0 21d ago
that makes me even more humbled :)
4.
by j0selit0 21d ago
author here - apologies for it not being clear. the idea here is: step 1: sparse index retrieval (FTS/BM25) - say with k = 10 step 2: re-rank the 10 records using embeddings the difference in this approach is during step 2, you convert
5.
by j0selit0 21d ago
you would also need to maintain multiple indexes in multiple languages. I never had to do that - but I assume it's a pain
6.
by j0selit0 21d ago
good one. yes, that's pretty much my experience with query rewriting as well
7.
by j0selit0 21d ago
to be fully transparent, I used LLM to review my draft yes. and interestingly enough, this article had tens of thousands of more views and estimulated significantly more discussions than my other, non-LLM written articles. so there's t
8.
by j0selit0 21d ago
and for the record, my last employer was still using gpt-4o and gpt-4o mini last year. and they are an F500 (not that it means anything, just for context).
9.
by j0selit0 21d ago
sorry if it came across as name dropping - the point I wanted to make is actually that F500s are chasing RAG (as in pure semantic search without any care for chunking strategies, evals etc) instead of starting with the basics. and for the r
10.
by j0selit0 21d ago
this is quite nuanced. in financial markets you have a combination of natural language questions that involve technical keywords / slang / acronym. and for these specific terms, an off-the-shelf embeddings model fails miserably.
11.
by j0selit0 21d ago
my personal experience - I have been involved with such projects for the last 2 years. interestingly enough, a lot of times such initiatives didn't take off because people/stakeholders were overcomplicating things and wanting to u
12.
by j0selit0 21d ago
I work on a really similar scenario. We ended up having to create a so-called "semantic layer" containing metadata (table and schema descriptions) and glossary terms. Still, there is a lot of work involved maintaining glossary ter
13.
Spice-ts: a TypeScript-native SPICE circuit simulator(github.com)
1 points by j0selit0 21d ago|0 comments
14.
Performance Excuses Debunked(computerenhance.com)
4 points by j0selit0 21d ago|0 comments
15.
by j0selit0 21d ago
I wish everyone thought like you, in my experience unfortunately it's not the case
16.
by j0selit0 21d ago
author here - that's an amazing idea. would be an insanely large article though - maybe will write up a series
17.
by j0selit0 21d ago
author here - thank you!
18.
by j0selit0 21d ago
author here - thanks, I'm honored you would use my agents :)
19.
by j0selit0 21d ago
I'm sorry is this ironic or not? doesn't sounds simple at all
20.
by j0selit0 21d ago
author here. at most companies I've worked for recently (F500) RAG is still quite trendy. this was what frustrated me a bit and motivated to write this article - along with other experiences that definitely relate with some of the folk
21.
RAG Is Simpler Than You Think(lighthousenewsletter.com)
516 points by j0selit0 22d ago|218 comments
22.
Benchmarking Agentgateway vs. LiteLLM's Rust Mode(agentgateway.dev)
2 points by j0selit0 23d ago|0 comments
23.
Distributed micro-LLM inference across three ESP32-S3 N16R8 boards with ESP-NOW(github.com)
1 points by j0selit0 23d ago|0 comments
24.
Cosine similarity is dead. Long live cosine similarity (2025)(lighthousenewsletter.com)
17 points by j0selit0 26d ago|2 comments
25.
by j0selit0 28d ago
Follow-up to my previous Copilot/mitmproxy post. While looking at the traffic I noticed Copilot’s own LLM requests used X-initiator: agent and didn’t consume premium quota. That made me curious what would happen if I changed my own req
26.
GitHub Copilot trusted a client header for premium-request billing(lighthousenewsletter.com)
3 points by j0selit0 28d ago|1 comments
27.
by j0selit0 1mo ago
thanks! corrected in the article
28.
We migrated the database behind every Vercel build(vercel.com)
2 points by j0selit0 1mo ago|0 comments
29.
by j0selit0 1mo ago
I was curious to understand how Copilot implements its harness, and also how I was exhausting my quota so quickly. End up going down a rabbit hole of intercepting its network traffic with mitmproxy. A few interesting things I found along th
30.
What I learned by putting GitHub Copilot behind a MitM proxy(lighthousenewsletter.com)
201 points by j0selit0 1mo ago|30 comments

More ›