https://news.ycombinator.com/item?id=43057907
Other than that a great article! Very insightful.
21–30 of 168 posts
https://news.ycombinator.com/item?id=43057907
Other than that a great article! Very insightful.
Isn't the input token number way more limited than that ?
This is part is unclear to me in the "non-Greenfield" part of the article.
Iterating with aider on very limited scopes is easy, I've used it often. But what about understanding a whole repository and act on it ? Following imports to understand a Typescript codebase as a whole ?
I’m curious, is adding “do not hallucinate” to prompts effective in preventing hallucinations? The author does this.
The first part of this, where you told it to ask YOU questions, rather than laboriously building prompts and context yourself was the magic ticket for me. And I doubt I would have stumbled on that sorta inverse logic on my own. Really great write up!
For example, rather than using Plasmo for its browser extension boilerplate and packaging utilities, I’ve chosen to ask the LLM to setup all of that for me as it won’t have any blindspots when tasked with debugging.
Given a 3 648 318 tokens repository (number from Repomix), I'm not sure what would be the cost of using a leading LLM to analyse it and ask improvements. Isn't the input token number way more limited than that ? This is part is unclear to me in the "non-Greenfield" part of the article. Iterating with aider on very limited scopes is easy, I've used it often. But what about understanding a whole repository and act on i…
This is all fine for a solo dev, but how does this work with a team / squad, working on the same code base? Having 7 different instances of an LLM analyzing the same code base and making suggestions would not just be economically wasteful, it would also be unpractical or even dangerous? Outside of RAG, which is a different thing, are there products that somehow "centralize" the context for a team, where all questions…
It did seem to take a while to index, even though my colleagues had been using Cursor for a while, so I'm likely misunderstanding something.
Given a 3 648 318 tokens repository (number from Repomix), I'm not sure what would be the cost of using a leading LLM to analyse it and ask improvements. Isn't the input token number way more limited than that ? This is part is unclear to me in the "non-Greenfield" part of the article. Iterating with aider on very limited scopes is easy, I've used it often. But what about understanding a whole repository and act on i…
Well, do you as a human have the whole codebase loaded in to your memory with the ability to mentally reason with it? No, you work on a small scope at a time.