2 ms·

I can give my broader feedback: - Codegen tools today are still not great: The lack of context and not using LSP really burns down the quality of the generated

by skp1995 2y ago

I can give my broader feedback: - Codegen tools today are still not great: The lack of context and not using LSP really burns down the quality of the generated code. - Autocomplete is great Autocomplete is pretty nice, IMHO it helps finish your thoughts and code faster, its like intellisense but better. If you are working on a greenfield project, AI codegen really shines today and there are many tools in the market for that. With Aide, we wanted it to work for engineers who spend >= 6 months on the same project and there are deep dependencies between classes/files and the project overall. For quick answers, I have a renewed habit of going to o1-preview or sonnet3.5 and then fact checking that with google (not been to stack overflow in a long while now) Do give AI coding a chance, I think you will be excited to say the least for the coming future and develop habits on how to best use the tool.

SparkyMcUnicorn 2y ago
> Codegen tools today are still not great: The lack of context and not using LSP really burns down the quality of the generated code Have you tried Aider? They've done some discovery on this subject, and it's currently using tree-sitter.
- skp1995 2y ago
  Yup, I have. We also use tree-sitter for the smartness of understanding symbols https://github.com/codestoryai/sidecar/blob/ba20fb3596c711860ba24cbed8fb05b5dddc25c8/sidecar/src/chunking/rust.rs https://github.com/codestoryai/sidecar/blob/ba20fb3596c71186... and also the editor for talking to the Language Server. What we found was that its not just about having access to these tools but to smartly perform the `go-to-definition` `go-to-reference` etc to grab the right context as and when required. Every LLM call in between slows down the response time so there are a fair bit of heuristics which we use today to sidestep that process.

SparkyMcUnicorn 2y ago

> Codegen tools today are still not great: The lack of context and not using LSP really burns down the quality of the generated code Have you tried Aider? They've done some discovery on this subject, and it's currently using tree-sitter.

skp1995 2y ago
Yup, I have. We also use tree-sitter for the smartness of understanding symbols https://github.com/codestoryai/sidecar/blob/ba20fb3596c711860ba24cbed8fb05b5dddc25c8/sidecar/src/chunking/rust.rs https://github.com/codestoryai/sidecar/blob/ba20fb3596c71186... and also the editor for talking to the Language Server. What we found was that its not just about having access to these tools but to smartly perform the `go-to-definition` `go-to-reference` etc to grab the right context as and when required. Every LLM call in between slows down the response time so there are a fair bit of heuristics which we use today to sidestep that process.