• @[email protected]
    link
    fedilink
    629 months 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

          • @[email protected]
            link
            fedilink
            89 months 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

          • @xmunk
            link
            39 months ago

            Those people are assholes and aren’t worth your consideration.

      • @[email protected]
        link
        fedilink
        59 months 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.

    • @[email protected]
      link
      fedilink
      99 months 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.

    • Jack Riddle
      link
      29 months ago

      You can’t do much worse than vim, so…

  • @[email protected]
    link
    fedilink
    409 months 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.

    • @[email protected]
      link
      fedilink
      149 months 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.

    • @[email protected]
      link
      fedilink
      119 months ago

      I have a project that I shared online, and the source code isn’t shared BECAUSE it sucks lol

      • @xmunk
        link
        69 months ago

        Well… share it - then you might get help making it suck less.

          • @[email protected]
            link
            fedilink
            19 months 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
      link
      fedilink
      English
      59 months 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.

    • @Jumuta
      link
      49 months ago

      Every proprietary software I touch makes me feel like it’s gooey and sticky and ewwww

  • Big P
    link
    fedilink
    English
    279 months ago

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

    • @[email protected]
      link
      fedilink
      119 months ago

      High five!

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

  • Dandroid
    link
    fedilink
    179 months 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
      link
      39 months 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.

      • Dandroid
        link
        fedilink
        29 months ago

        Oh I’m sure. But knowing that doesn’t make me any less self conscious about it.

        • @xmunk
          link
          19 months 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.

  • @xmunk
    link
    169 months ago

    Pre-heartbleed OpenSSL: “Hold my beer.”

  • @Aurenkin
    link
    79 months ago

    Oh man, I really thought that under the mask was going to be a bunch of open source software.

    • @xmunk
      link
      89 months ago

      Specifically OpenBSD. If you browse into the Windows System32 folder you’ll eventually trip over an etc directory… inside you’ll find a file called hosts.

      I wonder why…