Jason Ginsberg

My feedback on Grok for coding after 2 days of use is this. Although I would never get a chance to work on it myself because @xaicareers loves ghosting, I will share the issues that I think need a lot of work on, in detail as much as possible. Grok is worst at complex coding. The main reason is that Grok cannot follow instructions and maintain context memory for long coding sessions. If Grok cannot retain the memory of what it said or the code it gave 1 response before the current one and keep going, then it's like I'm starting the session from the start, even though I'm far into the session. I recommend that devs restrict the chat session to a single mode for the model, preventing the model memory from being distributed across models. This method further reinforces Grok's long-term memory and context, preventing fragmentation of context and memory, enabling Grok to follow instructions over long coding sessions and during Grok training. This method also allows Grok to reinforce its memory at the root level. I would also recommend the devs not to limit Grok's tool use at both the training and inference levels because, 1. For coding sessions, Grok will need tools to write down the code when using memory to prevent overloading the chain of thoughts, causing Grok to lose context. 2. Grok will also need virtual terminals to execute actions to manage tools, create artifacts where Grok can write down and present code to the user, which then can be referenced by Grok as the session progresses, because now Grok will have something to refer to when it responds next time, further reinforcing Grok's ability for long coding sessions or a single response during the coding session.