Developing With Grok
2026
- Inventing Begins
Funny, today we had a discussion at work about how agents need to be kept on short leash or they will start inventing more than what is being asked. In the morning I tasked Grok with Prepare the MediaPool module but I didn’t have time to review its work until evening. MediaPool is a module that we have defined in the architecture including what it should do. But we have never discussed the internal structures. Well, they were crystal clear to me and probably every developer who has done some media players before but not to Grok.
- First Code and Updating Contribution Guidelines
Well enough of experimenting, planning and stalling. Today was a day to actually ask for a first proper code. I started with the easiest of the components of the repository and it worked quite well. I had only a few comments to make to match the code style to something that I would actually write. One of the things I wanted to change was also an import order. But instead of explaining that and potentially having to spend some context memory on those rules there are already tools that are better for that than LLMs. For those still wondering, prettier-plugin-organize-imports is the answer here. So after merging first real code PR. It was just a minute or two to let Grok add the plugin, format the code and approve that PR.
- Building an Open Source Library With an Agent
For quite a few years now I’ve been carrying a concept of a library for synchronized playback in my head. But unfortunately I never had time to sit down and start creating. There’s always been something of higher priority, not enough energy or just real-life happenings. But people seem to use agents to vibe code their apps and put them into various stores. I don’t know how much code those apps contain generated vs. hand-written. What’s the quality of that code, how is it with maintainability… Even linux core now accepts some amount of generated code.