Just to clarify, I google a lot while coding, but one thing I learnt from my engineering degree is that is there is no ‘best’ solution.

  • x1gma@lemmy.world
    link
    fedilink
    arrow-up
    3
    ·
    26 days ago

    “Googling a lot while coding” is not even remotely close to vibe coding, please don’t gaslight yourself into that.

    When you read up on things, you know what you’re looking for. You read a potential solution (e.g. part of a documentation, an example, someone else’s solution, a solution to a similar problem), you think about it and transfer that to your own problem, with your own code, with your own thoughts.

    Using AI support is totally fine too - it’s a smarter code completion, nothing more. It might spit out something wrong, something partial, something good. You might ignore it as with the regular completion. In the end, it’s still you thinking about it, modifying it until it works, and doing your thing.

    “Vibe coding” is basically saying tech jesus take the wheel. And it might go well for someone who cannot code, who managed to create their small game or some website. It will go horribly wrong for any project handling user data, sensitive data, or something that needs to be maintained after. We’ve had more than enough examples of that.

  • NotSteve_@lemmy.ca
    link
    fedilink
    arrow-up
    1
    ·
    26 days ago

    I use AI for work and personal projects, sometimes even letting it generate file structures for me but damn does it ever need a lot of tweaking after generation to both work and be maintainable.

    I don’t know how anything it spits out even works for those who just purely vibe code since it’s usually either wrong or broken.

  • MonkderVierte@lemmy.ml
    link
    fedilink
    arrow-up
    0
    ·
    edit-2
    26 days ago

    Would you visit a house built by vibe architecting? Me neither.

    And as soon as the vibe software goes online, your users will not be the only victims anymore.

    • KeenFlame@feddit.nu
      link
      fedilink
      arrow-up
      1
      ·
      26 days ago

      And who will? You are crediting too much on the idiotic trend. Nobody has successfully used it

  • MTK@lemmy.world
    link
    fedilink
    arrow-up
    0
    ·
    25 days ago

    Mark my words, a decade from now vibe coding won’t be a thing because it will literally be calked regular coding and there will like “coding experts” or some shit that would basically be normal programmers that are good at it. And they will be tge only ones that can really solve novel problems.

    Or, AI will actually get to a point of being a real programmer and not a (very cool but still just a) tool.

    But just to cover my bases, it might also be neither.

    Welcome to my TED talk on how to never be wrong!

    • Buckshot@programming.dev
      link
      fedilink
      arrow-up
      1
      ·
      25 days ago

      I like to think this whole thing will collapse and there’ll be a massive demand for real programmers to clean up/rewrite all the AI slop.

      But your thing seems more likely.

    • fckreddit@lemmy.mlOP
      link
      fedilink
      arrow-up
      1
      ·
      26 days ago

      Yup. It is real. There are people who genuinely believe, it is the future of coding. That is why I posted the tutorial. /s

    • Pieisawesome@lemmy.dbzer0.com
      link
      fedilink
      English
      arrow-up
      0
      ·
      26 days ago

      Yes.

      I “vibe code” anything that is throwaway. If it’s throwaway code I don’t care about the quality, I just want the end result.

      For everything else, I don’t vibe code.

      There are definitely people who use AI as a crutch for their lack of technical skills. It’s the same folks who used to try to get coworkers to “help” and slowly built their tickets by cycling through teammates.

      • Ephera@lemmy.ml
        link
        fedilink
        English
        arrow-up
        1
        ·
        25 days ago

        But like, does that happen often for you, that you need a piece of code that’s gonna be thrown away?

        I always feel like if code exists, it’s not gonna be thrown away, so it’s a good idea to make it maintainable. But I do probably have somewhat of a bias…

      • ulterno@programming.dev
        link
        fedilink
        English
        arrow-up
        1
        ·
        edit-2
        25 days ago

        By definition, it is a markup language, but I have seen recently that it has a few elements that kinda feel like programming.

        Though you do tend to require some JS to complete the logic.


        On the other hand, just because someone uses a non-programming language, does not surely make them not a programmer

          • ulterno@programming.dev
            link
            fedilink
            English
            arrow-up
            0
            ·
            25 days ago

            It’s nice to be the case.

            But doing all the programming in CSS is too hard for a on-shot hobby-site maker like me.

        • Dr. Moose@lemmy.world
          cake
          link
          fedilink
          English
          arrow-up
          0
          arrow-down
          1
          ·
          25 days ago

          Writing html is absolute programming in 99% of the cases. You program the structure of a web page, even more so if you use templating or integrate structure with js functionality.

          • ulterno@programming.dev
            link
            fedilink
            English
            arrow-up
            1
            ·
            25 days ago

            program the structure of a web page

            In a loose sense, yes.

            But then someone could also say that when making LATEX templates is programming the structure of the documents.

            I prefer calling it markup, because, even though people might prefer calling it ‘programming’, due to people’s high esteem perception of the word, if you look at it from a neutral standpoint, markup is a word that represents the actual work, much more closely.

            e.g. I use Qt Designer[1] to create UI stuff, and in some cases QML[2] and if I were to only be defining placements, shapes, sizes and colours of elements, I would like to call that part as marking-up the UI [3], while the part where I define functions, timers and connections would be the programming part.


            1. which is a UI to create UI stuff, which creates an XML definition of the final UI to be generated ↩︎

            2. which is based on JS ↩︎

            3. of course I don’t because nobody would understand, but if people did care about the word (and I kinda like the word), it would be more accurate ↩︎