HelixNotes is completely free, open source, with no bloat. Your notes should be yours.

So we made sure they are. https://helixnotes.com/

  • rockyroad226@lemmy.worldOP
    92·
    2 days ago

    Thanks for asking. Yes, we use AI as a tool in our workflow. The difference between our workflow and ‘vibe coding’ is that we can catch and fix problems. We’re not just shipping whatever an AI produces and hoping it works.

    • mnemonicmonkeys@sh.itjust.worksEnglish
      1·
      2 hours ago

      That’s still rather vague tbh. There’s a pretty big spectrum of how involved an AI gets beyond just letting the AI do everything, and the line between ‘vibe coding’ and not is blurry and changes between individuals.

      Are you treating the AI like a glorified StackOverflow/Google to get suggestion and then manually writing/adapting the code yourself? Are you letting the AI do all the coding and running a lot of tests? Is it something in between or outside those examples?

      I’m not trying to string you up, it’s just that communication and disclosure are important in FOSS

      • rockyroad226@lemmy.worldOP
        1·
        7 hours ago

        Fair point. To be more specific we’re somewhere in between. AI writes a lot of code for us, but there’s a developer in the loop who reads every line and understands what it’s doing. We still make the call on whether it stays unlike the traditional vibe coder who doesn’t know what to look for. Hope that clears things up a bit.