Thread

1. alexpotato · 1789933586 · focus · HN ↗

   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.

   1. botacode · 1789937133 · focus · HN ↗

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

      1. ThalesX · 1789938975 · focus · HN ↗

         [dead]

         1. dlederle · 1789939908 · focus · HN ↗

            Do all that, when you arent operating a vehicle that can kill me and my family

            1. ThalesX · 1789944164 · focus · HN ↗

               [dead]

               1. matkoniecz · 1789946399 · focus · HN ↗

                  trying to code while driving is a terrible idea, and it is not changed by whether complaining it about it is virtue signalling

                  "is a lot higher than the chances" - you killing people due to such stupid idea is far far worse, so that despite it being less likely it has far greater negative impact

                  1. ThalesX · 1789965924 · focus · HN ↗

                     [dead]

Unofficial Hacker News client; not affiliated with Y Combinator.