|
|
|
|
|
by scuol
398 days ago
|
|
It still seems to have the problems most other LLMs suffer with except Gemini: it loses context so quickly. I asked it about a paper I was looking at (SLOG [0]) and it basically lost the context of what "slog" referred to after 3 prompts. 1. I asked for an example transaction illustrating the key advantages of the SLOG approach. It responded with some general DB transaction stuff. 2. I then said "no use slog like we were talking about" and then it gave me a golang example using the log/slog package Even without the weird political things around Grok, it just isn't that good. [0] https://www.vldb.org/pvldb/vol12/p1747-ren.pdf |
|
I'll say that grok is really excellent at helping my understand the codebase, but some miss-named functions or variables will trip it up..