I told my boss I had an idea for a program that could improve efficiency across much of the business, and he let me build it on company time. In the long term, he wanted to be able to sell it to other companies. However, the program never got implemented due to personnel mismanagement, and I’d rather be able to post it on my github under a free licence so I can use it as a resume item, and at least someone would have the chance to actually use it. It’s all still in my head, and I could write it again if I wanted. If I do, is it illegal to publish it? What if I write it in a different language? Do I need to change the variable names? I did plenty of research and planning on company time to build it, and it’s not like I can research it again, it’s all still in my head.

  • BB_C
    161·
    1 year ago

    Meh, everyone scaring you into thinking you don’t own your own mind.

    Assuming your boss is not the dangerous kind (beyond legal threats), and if the goal is to make it FOSS, then do it using an alias first. Do it differently. Use components/libs/algos from other people at first, even if they are not perfect. Make those parts easily pluggable/replaceable which would be good design anyway. The code then wouldn’t be wholly yours, not even your alias self.

    You can join the project later with your real identity as an interested domain expert (maybe a bit after not working for the same boss). Start contributing. Become a maintainer. And maybe take over after a while. You can start replacing non-optimal components/libs/algos with better ones piecemeal.

    Oh, and if Rust wasn’t the choice of implementation, use it this time.

    • 0x0
      151·
      1 year ago

      Also, don’t use company hardware; don’t do it during working hours (especially commits - if you’re paranoid, use tor) either; resist the temptation of giving the old code a look, do it from memory.

      • BB_C
        8·
        1 year ago

        don’t do it during working hours (especially commits - if you’re paranoid, use tor)

        I wanted to mention not using personal emails or committing from home IP addresses, but thought that was needless to say.

      • Blackthorn
        3·
        1 year ago

        I’d say it suggests it’s “legally” the wrong thing to do.

      • MachineFab812@discuss.tchncs.de
        3·
        9 months ago

        “Make those parts pluggable/replaceable which would be a good design anyways”.

        Following best practices = Morally Wrong?
        Sure, fren, whatever you say.

        The only reason OP might not have done it this way in the first place would have been to save the company worrying about licensing, or getting shitty with OP about not using enough orignal/proprietary code to ensure lock-in with future clients … is THAT somehow morally superior in your book?

        • lemmyvore@feddit.nlEnglish
          41·
          1 year ago

          I just mean that the amount of subterfuge that’s been suggested in this thread suggests these people feel that something’s wrong. You don’t normally have to go to such lengths to hide your identity on GitHub.

          Let’s be honest, deciding later that code they wrote for someone should be repurposed behind their back is rather underhanded. And making it open source rather than spinning their own company doesn’t make it more palatable.