← Back to context

Comment by alexpotato

3 hours ago

So I ended up doing something similar:

- Create a Git Hub project board for issues

- Connect Grok to the above

- Use Grok voice mode to take ideas, have Grok refine them with me and then save them as issues

- Created slash commands in OpenCode like /ni (new issue), /do (do an issue), /curr (what is the current issue), /done (self explanatory)

- I generally tell the OpenCode instance to /do <number> and then off it goes

This give me several benefits:

- I can use Grok Voice while walking or driving to develop and test ideas

- I can lose my entire local OpenCode setup but still have relevant data in the issues

- multiple machines can read from GitHub

- I could go even further and have separate user accounts for each of my bots.

Having been both a PM, dev, SRE and manager, this really does feel like managing a team of devs.

8 comments

alexpotato

Reply
mentalgear  2 hours ago

and do you ever look at the code afterwards? The 'software factory' gets exponentially nastier the longer it is kept running without someone with actual experience 'shoving it' back in shape ever so often ... and even then.

  • le-mark  1 hour ago

    Sounds like token burn maxing to me. Ie end up with a lot of “not quite” prototypes soooo try again?

botacode  2 hours ago

don't work while driving, you're putting other people at risk by being distracted

  • ThalesX  2 hours ago

    Bro this board is called Hacker News. Let us shove the needle in our prefrontal cortex and use dolphin white matter to hack into SpaceX's network to issue commands to Grok using some ancient sumerian dialect and keep this shit signaling for your Washington Post interview.

andyjohnson0  2 hours ago

> I can use Grok Voice while walking or driving to develop and test ideas

Musk would be so proud. Do you by any chance drive a cybertruck too?

Seriously, don't do this while you're driving. Or even while your car is driving. Its dangerous to be distracted in that situation.