Skip to content

Comment on I built a recipe app in Germany: no ads, no tracking, saves recipes from websites, videos and photos (and more)

You are viewing one comment and its replies. View all comments · View the comment above

Comments

  • So it is vibe coded. Just because you have experience in the field doesn’t change that the code is mostly created via vibes.

    -5
    • I didn’t look at the app, and I certainly won’t use non open source app, but there is difference between vibe coded and ai assisted. Maybe OP can share how exactly he uses the AI?

      7
      • Sure, I’ll try to be as transparent as I can. In my experience as a software developer, over the years there’s been a lot of reinventing the wheel. Things like dialogs, menus, panels, lists, drawers opening and closing, etc. are pretty standard stuff. I use Vuetify for the basic Material Design components and Tailwind for styling, and sometimes getting the two to play nicely together means overriding Vuetify’s CSS, which can be pretty tedious. That’s the kind of thing I’m happy to let AI handle.

        Another example, I recently added bulk deletion to the library. The whole flow around selecting multiple items, showing checkboxes, having a “select all” option, keeping track of what’s selected, etc. is such a common pattern that AI can put most of that together very quickly. For stuff like that, I don’t really see a difference in quality whether I write all of that myself or have AI help with it.

        I write a lot of the text in the app myself, but I can be a bit too verbose, so AI helps me shorten and tidy it. The translations were done with AI and mostly checked by me, and the Greek one was also checked by my friend’s mother. I would like to add more European languages, but at the moment I don’t have a good way to verify them properly.

        For things where the actual behavior matters more, like making sure users can only access what they’re supposed to, or that every ingredient ends up in a valid recipe step and nothing gets lost, I sometimes start by having AI write the tests. I go through those first and make sure they actually describe what I want the feature to do before building it, as in “test-driven development”. AI has a tendency to rewrite tests to match its own implementation if you let it, which is how you end up with bad code.

        There are of course more examples, but that would probably go too far into detail. So yeah, AI helps me with development, and I still write and fix code myself. The parts that always stay with me are deciding what to build, how it should work and look, and making sure it actually behaves the way I intended.

        This turned out to be longer than I expected, but I know this is a sensitive subject and I wanted to be as transparent as possible.

        1
        • Hi, thanks for the long reply, I really appreciate it. As a long time dev myself I can understand why you do with AI most of what you do. Although I wouldn’t really let it generate code myself (except for tests that are later properly reviewed). I know that development may feel a lot like reinventing the wheel, but that is also the beauty of it, you do it once, twice and then you know how to do it by heart and there is no better feeling than having a blank slate and then just… writing and the whole time you know what comes next and it doesn’t mean you write the same code, you improvise. And then having something generate code feels like losing control over it and there is one thing I don’t really agree with. If I write the code myself, its neat (by my standards) and compact. If it is generated, unless I’d go through it and change it heavily, its bloated and hard to read. Personally I would rather write my code 10 times for 10 projects even if a lots of it is the same and even if I have to re-discover stuff rather than generate it and then do lengthy boring reviews and fixes. I don’t really like going through existing code written by somebody else, that part is the most boring. But I understand not everybody is the same. Personally, for me, the biggest turn off on your project is that I can not verify that it does what you say it does = I won’t use it. Anyway, I wish you good luck with the project and if you enjoy working on it that is the most important thing! ignore opinions that tell you to do things differently :)

          1
          • Thank you too for the thorough response and your kind words! I have to say, I think we agree on quite a lot.

            I still remember the first time programming really “clicked” for me. It’s almost like your brain changes and you start thinking in a different way. Giving instructions to a machine and then seeing it do exactly what you wanted was one of the things that made me fall in love with software development. The idea that you can click a button and have a machine do a thousand things for your users that would otherwise take days/weeks/months is still amazing to me. And of course there is also that sense of pride in having built something that helps other people and makes their lives easier.

            But one thing I really don’t enjoy is doing the same work over and over again. I like inventing things and solving problems, not solving the same puzzle hundreds of times. I remember back in the SVN days, pre-git era, I lost some of my code a couple of times and having to recreate everything was just painful.

            And I also agree that there is a kind of poetry in nice, clean code. I think there is always a balance between craftsmanship and actually getting something finished, though. That’s probably something engineers and artists both struggle with. You can work on a book for 50 years trying to make it perfect, but if you never release it, nobody will ever get to read it. But, I see the divide, having a writer use AI to write part of the book is just ridiculous. Maybe my analogy wasn’t the best!

            I had the idea for this app for quite a while, but I never really managed to get around to building it. It’s just something I do on the side, and with some help I was finally able to get it done. Every now and then I add something new, mostly because I want it myself. And like I said, if somebody else wants to use it too, they’re more than welcome to.

            Regarding not knowing what the app actually does, you’re definitely right. It’s almost impossible to know for sure. I’m the same way with mobile apps. You never really know how much data they’re collecting or what they’re doing with it. In this case, my thinking was that you’re basically only sending URLs, or you can even just paste text, and then you get a clean recipe out of it. There isn’t really any other personal data you need to send. You can also see from the network calls that there isn’t any tracking or anything like that. I hope this isn’t sounding like I’m trying to convince you to use it. I just wanted to explain how I thought about that part.

            0
    • We might have different definitions of what vibe coding is, but fair enough. What’s your concern with it? If it’s quality or security, I’m happy to answer whatever you want to know.

      0
      • Lemmy hates AI (and for good reason). Just something to keep in mind when posting here.

        8
      • What’s your concern with it?

        The means don’t justify the ends. Also it causes brain rot.

        2

Sign in to comment. Sign in