• QuazarOmega@lemy.lol
    654·
    1 year ago

    On the other side there’s people that genuinely use that as an excuse and say “they’ll open source after they cleaned up the code”. Why they couldn’t clean it up in the clear is beyond me, no one will shame you for your code, just sharing it under a free license is admirable in and of itself

          • QuazarOmega@lemy.lol
            8·
            1 year ago

            That’s awful, I guess I should consider myself lucky that nobody looks at my repositories then. But still, if someone does they’re the assholes, you shouldn’t feel bad about it, you should actually tell them to fix it themselves if they’re so good

      • VikingHippie@lemmy.wtf
        6·
        1 year ago

        Those are the kind of people who will always find something to ridicule or complain about, though, so you should never let their hypothetical bitching affect your decisions.

    • ______@lemm.ee
      9·
      1 year ago

      I was watching a YouTuber going over a major revision update for a framework or something and he said “I skipped over the part where I was coding this” nah dude, I wanna see that as well. What did you try and how did it go.

      So much weird ego in coding.

  • ______@lemm.ee
    456·
    1 year ago

    Asshole take: if you share your project online but not the source code I immediately think your code sucks.

    Let’s be real your clone project is not something a venture capitalist is going to invest in, there’s literally no reason to hide it but shame. Shame of sinful and bad code.

    • captainteebs@lemmy.ml
      14·
      1 year ago

      This applies to any project, really. At my workplace, if someone refuses to let other teams look under the hood of a product, 95% of the time, it’s because their code is absolute garbage, but their leaders didn’t want to wait so they pushed it to prod and now it’s up to some junior employee to fix all the shit that blows up in prod.

      And just for closure, 5% of the time, it’s because there actually is no product at all.

          • ______@lemm.ee
            1·
            1 year ago

            One of the best devs I’ve ever had the pleasure to meet chatted with me about the worst code we’ve ever wrote. We even provided links to the specific repos and lines. Nothing to be ashamed of.

    • HTTP_404_NotFound@lemmyonline.comEnglish
      61·
      1 year ago

      For certain projects I monetize, there are reasons I don’t share the code.

      Patents don’t magically find people infringing your intellectual property. The owness is on you.

      That being said, I have bills to pay, and mouths to feed. Giving my solutions away for free, doesn’t help those issues.

  • Big P@feddit.ukEnglish
    26·
    1 year ago

    I make all my sucky code public because I’ve never seen a codebase that doesn’t suck in some way

    • MajorHavoc@lemmy.world
      11·
      1 year ago

      High five!

      My code might be garbage, but I’ve learned that no one will notice in this aisle of trash heaps.

  • Dandroid@dandroid.app
    181·
    1 year ago

    I have a private repo on GitHub that is private for this reason. I made it in a weekend for fun, and it’s honestly so bad. I have spent way longer fixing dumb mistakes that I spent developing the main features in the first place. But I learned a lot while doing it (and fixing it), and my current project that I’m working on is much, MUCH better. I do have it in a public repo.

    • xmunk@sh.itjust.works
      3·
      1 year ago

      Nobody that isn’t an asshole is going to shame you over dirty code - and if you make it public maybe someone will help you clean it up.

        • xmunk@sh.itjust.works
          1·
          1 year ago

          I like your code. I’m a senior developer who is fastidious about code form and will comment on bad form on any PR put in front of me because readability is the second most important characteristic of code for maintainability. Still, I’ve written uglier code. Take this comment and print it out if you want to, it’s a writ of permission to write ugly code just as long as you eventually plan on cleaning it up.